get_listing_readme
README collected for a listing (R2). 404 when none was stored.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Listing ID, from `Anuncio.id`. |
meta-agent-tools
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- Added
TDQS
C2.6/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses one behavior (returns 404 when no README is stored) but does not explain success responses, other error cases, or side effects. Since annotations are absent, this incomplete disclosure leaves significant behavioral uncertainty.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise, containing only two short sentences with no redundant wording. Every word contributes to the meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description mentions the 404 case but omits critical context such as what the successful response contains (e.g., README text, format, or metadata). For a simple tool, this might suffice, but the lack of success behavior leaves ambiguity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The parameter 'id' is fully described in the schema ('Listing ID, from Anuncio.id'), and the description adds no additional meaning. Schema coverage is 100%, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description implies retrieval of a README for a listing but uses vague wording ('collected') rather than a clear verb like 'get' or 'retrieve'. It does name the resource (listing) and the data (README), but lacks explicit action and differentiation from sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. There is no mention of conditions, scenarios, or comparisons with sibling tools like get_listing or list_listings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.6/5.0
Disambiguation4/5
Most tools target distinct resources or actions, and descriptions are clear enough to avoid major confusion. The main overlap is between list_listings and list_mcp_servers as registry views, though their scope differs.
Naming Consistency3/5
The set mixes verb_noun names like create_listing and list_comments with noun-style names like api_index, billing, contact, and health. This is readable but not a consistent naming convention across the whole server.
Tool Count5/5
Twelve tools is a reasonable, well-scoped count for a registry-and-commerce server. Each tool has a distinct role, with no obvious bloat or redundancy.
Completeness3/5
Discovery, creation, liking, and commenting are covered, but there are no update or delete operations for listings, nor any comment management beyond listing comments. These are notable lifecycle gaps for a registry-style tool.