Skip to main content
Glama

What people report for a place

community_figures
Read-onlyIdempotent

Figures people report for themselves about a place on Borgo, after automated review: rent by bedrooms and area, everyday prices, take-home pay by kind of work and a 1 to 5 rating of living there, each with its median (a rating: mean), middle half from 3 entries, count, months and the official figure beside it where one exists. Community data, CC BY 4.0; never mixed into official figures or scores. Covers the snapshot's cities and the towns on Borgo's map.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>"
    },
    "name": "community_figures"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity id (turin-it) or name ('Turin', 'Palermo, IT')

Output Schema

NameRequiredDescriptionDefault
reportVersionYesThe report's shape version (now 2.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the bar is lower. The description still adds real value by disclosing moderation ('after automated review'), licensing (CC BY 4.0), and the guarantee that community data is never blended into official figures or scores — an important integrity trait — but says nothing about freshness, pagination, or limits on returned entries.

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 opening sentence packs every metric plus statistical qualifiers (median, mean for the rating, middle half from 3 entries, count, months) into a dense, hard-to-parse clause. The provenance and scope sentences are well placed, but the statistical detail is arguably redundant given an output schema exists, so the text is longer than its informational value warrants.

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?

An output schema exists, so the description need not explain return shapes, and annotations cover the safety profile. It covers provenance, licensing, data separation, and geographic scope — enough for a single-parameter read tool — with the only notable gap being sibling routing guidance.

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?

Schema coverage is 100% and the single city parameter already documents accepted formats (id vs name), so the baseline is 3. The description adds marginal meaning by clarifying dataset coverage ('the snapshot's cities and the towns on Borgo's map'), telling the agent that not every city necessarily has data.

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 states a specific resource (community-reported figures about a place on Borgo) and enumerates the categories returned: rent by bedrooms/area, everyday prices, take-home pay by work kind, and a 1-5 living rating. It also distinguishes the data from official figures, which separates it from siblings like net_pay and get_city, though the top-level verb ('reports') is implicit rather than stated.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer it should call this for crowd-sourced rather than official statistics, and the closing sentence clarifies geographic scope. There is no explicit when-to-use/when-not guidance and no mention of how it relates to submit_figures or compare_cities, so routing decisions are left to inference.

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.