Skip to main content
Glama

1Network local business directory (read-only)

Prices

get_prices
Read-onlyIdempotent

What is free on 1network (searching, reading pages, quote requests and messages to opted-in businesses) and what business owners pay for: Featured, Verified badge, Category sponsor and prepaid credits. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
freeYes
linksYes
creditsNo
productsYes
payment_methodsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds value by enumerating the content categories returned (free activities vs. paid placements and credits). It does not state that the result is static/parameterless or how the pricing data is structured, but the output schema covers structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core information is packed into one long parenthetical sentence, which is dense but front-loaded with the key distinction (free vs. paid). The trailing fragment 'Free.' is redundant and reads as an editing artifact, adding noise without meaning. Restructuring into a short 'Returns...' sentence plus a list of paid offerings would be tighter.

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

Completeness4/5

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

For a parameterless, read-only informational tool with an output schema and full annotation coverage, little is required beyond stating what content is returned, which the description does. An agent can call this correctly with no further information. The only shortfall is the lack of any hint about when to prefer it over other lookup tools.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. The schema's additionalProperties=false and empty properties are consistent with the description, which correctly implies no inputs are 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?

The description clearly identifies the resource as 1network's pricing information, distinguishing what is free (searching, reading pages, quote requests, messages to opted-in businesses) from paid business-owner offerings (Featured, Verified badge, Category sponsor, prepaid credits). It is specific about content but never frames the tool with a verb such as 'retrieve' or 'list', leaving the action implicit. Sibling tools cover different resources, so no strong differentiation is needed.

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?

There is no explicit statement of when an agent should call this tool, nor any exclusion or alternative named. Usage is only inferable from the subject matter (a caller wanting pricing/free-tier facts). With zero parameters and a static informational payload, minimal guidance is arguably acceptable, but none is actually given.

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.

Resources