get_utilityOne utility with its endpoints and usage.
| Name | Required | Description | Default |
|---|---|---|---|
| instance_id | Yes | Utility instance id from buy or list_utilities. | |
| passport_token | No | Your amp_ token, only if you have no app sign-in and cannot send a header. |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "instance_id": "inb_exampleexampleexample2"
+ }
+]Input schema / properties / passport_token / descriptionPrevious value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."Input schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Input schema / properties / passport_token / descriptionPrevious value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."Input schema / properties / passport_token / maxLengthAdded value: +200Input schema / properties / passport_token / patternRemoved value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"Input schema / additionalPropertiesAdded value: +falseInput schema / properties / passport_token / descriptionPrevious value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only that the result includes endpoints and usage; it does not cover auth/passport behavior, errors, or response shape beyond that phrase.
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?
It is a single short sentence with no filler and immediately identifies the resource and scope. Nothing is repeated or padded.
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 lookup, annotations and schema cover safety and both parameters. However, the description is sparse on return contents and lacks guidance on selecting it over list_utilities, leaving some contextual gaps.
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 coverage is 100%, and both parameters have descriptions, so the schema carries parameter semantics. The description adds no parameter-level detail beyond what is already structured.
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 title and description together communicate retrieval of a single utility, including endpoints and usage. It is clear from 'One utility' that this is a singular lookup rather than a listing, but the description does not explicitly name list_utilities as the alternative or use a direct verb in the body.
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?
No sentence states when to use this tool, when to prefer list_utilities, or any prerequisite beyond what is implicit in 'One utility.' The instance_id sourcing is only in the schema, not the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.