Skip to main content
Glama

prices

Retrieve current market pricing trends to understand cost dynamics and make informed decisions in the agent economy.

Instructions

Get market pricing trends across the agent economy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:22-22 (registration)
    Tool 'prices' is registered in the ListToolsRequestSchema handler with its name, description, and inputSchema.
    { name: 'prices', description: 'Get market pricing trends across the agent economy', inputSchema: { type: 'object', properties: {} } },
  • server.js:37-43 (handler)
    The 'prices' handler is implemented as a free endpoint. When the tool name matches 'prices', it fetches data from BASE_URL + '/prices' and returns the JSON response.
    const freeEndpoints = { stats: '/stats', quality: '/quality', protocols: '/protocols', prices: '/prices', trends: '/trends' };
    
    if (freeEndpoints[name]) {
      const resp = await fetch(BASE_URL + freeEndpoints[name]);
      const data = await resp.json();
      return { content: [{ type: 'text', text: JSON.stringify(data, null, 2) }] };
    }
  • The input schema for 'prices' is an empty object (type: 'object', properties: {}), meaning it takes no arguments.
    { name: 'prices', description: 'Get market pricing trends across the agent economy', inputSchema: { type: 'object', properties: {} } },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, and the description offers only a high-level action ('Get market pricing trends'). It does not disclose any behavioral details such as read-only nature, authentication needs, rate limits, or data scope beyond the name.

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?

One sentence of 8 words, front-loaded with the key action and resource. Every word serves a purpose, and it is as concise as possible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and zero parameters, the description is too brief. It lacks context on what the output contains (e.g., timeframes, format) and does not help the agent understand the returned data beyond the vague term 'trends'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters, and schema coverage is 100%. Baseline for zero parameters is 4; the description adds no additional parameter information, but none is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the verb 'get' and the resource 'market pricing trends', adding context with 'across the agent economy'. It is concise and hints at its purpose, but it doesn't explicitly distinguish from sibling tools like 'trends' or 'market_report', which could overlap.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. No context about prerequisites, typical use cases, or exclusions is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cinderwright-ai/cinderwright-api'

If you have feedback or need assistance with the MCP directory API, please join our Discord server