generate_addressGenerate a synthetic Nigerian address for testing or development by specifying a region: east, west, north, or south.
Generates a synthetic Nigerian address. Pass a region to place it in that part of the country.
| Name | Required | Description | Default |
|---|---|---|---|
| region | No |
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes |
Changes observed during successful MCP inspections.
v2.1.0Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / properties / regionAdded value: +{
+ "enum": [
+ "east",
+ "west",
+ "north",
+ "south"
+ ],
+ "type": "string"
+}v2.0.0Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "value": {}
+ },
+ "required": [
+ "value"
+ ],
+ "type": "object"
+}v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that the output is synthetic and Nigerian, and that region influences placement. It does not explain randomness, output format, or behavior when region is omitted, but the simplicity of the tool and annotation coverage keep this at a solid 3.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no filler. The first sentence front-loads the core purpose, and the second provides the only parameter guidance. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only generator with one optional parameter and an output schema, the description covers what it does and how to influence output. It could mention the optionality of region or typical address components, but the output schema supplies return details and annotations cover safety, so the gap is minor.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It clarifies that 'region' refers to a geographic part of Nigeria, giving meaning to the enum values. However, it does not state what happens when the optional region is omitted (e.g., random choice), which is a minor gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('generates') and resource ('synthetic Nigerian address'), which clearly differentiates it from sibling tools like generate_states and generate_lgas that produce related but distinct geographic entities. The 'Nigerian' qualifier further narrows scope, leaving no ambiguity about what the tool produces.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives guidance for the region parameter (use it to place the address in a part of the country), which is helpful. However, it does not explicitly contrast with alternatives like generate_states or generate_lgas, nor does it state when to prefer this tool over those. Usage is implied but not made explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.