# Natural Language Metadata
## Introduction
Natural Language Metadata allows the definition of any number of custom Key-Value text metadata in order to better describe a Project Element.
## Configuration
**Define the Name**
Give a specific and descriptive name to your natural language metadata. This name helps to infer the metadata's purpose and distinguish it from other metadata. It should clearly indicate what the metadata represents.
**Key-Value Pairs**
Add the actual metadata using key-value pairs:
* **Key**: Define a key to easily refer to a value.
* **Value**: Describe the metadata in text form associated with the key.
By clearly naming and defining key-value pairs, you can effectively manage and utilize natural language metadata within your smart contract.
## KeyValue
Metadata Key-Values are custom metadata that can be attached to a Project element in order to better describe it.
The Metadata Key defines a string to easily refer to the Value of the metadata.
The Metadata Value defines the information held by the metadata. This is a free text field, so any type of information can be stored, as long as it is in text form.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.astrakode.tech/akb-wiki/astrakode-wiki/smart-contract-ide/technologies/ethereum/components/natural-language-metadata.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.