Skip to main content
Glama

Venue atmosphere verification, Bitcoin timestamp (PlaceProfile, paid)

corpus_info

FREE. Scale, coverage and freshness of the PlaceProfile venue corpus. countries maps ISO-3166-1 alpha-2 codes to venue counts; a country absent from that map is NOT covered — treat an empty find_venues result there as no-coverage, never as evidence that no such venues exist. line_count is not a marketing claim: it is the line count of the downloadable manifest, independently checkable.

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": "corpus_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses cost (FREE), the authoritative meaning of the countries map including the absent-country edge case, and that line_count is an independently checkable manifest line count rather than a marketing figure. It omits any statement about response size, freshness representation, or caching/rate behavior.

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?

Three sentences, front-loaded with the cost signal and the resource being described, then two field-level clarifications that each carry non-obvious meaning. No filler and no restatement of the tool name.

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 metadata tool with no output schema, the description must explain the returns, and it does so for countries and line_count. The gap is 'freshness,' which is promised in the opening but never explained in terms of how it appears in the response, leaving one advertised field undocumented.

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 and the schema is an empty object, so there is nothing parameter-level to explain; the baseline of 4 applies. The description does spend its space on output-field semantics instead, which is the relevant substitute here.

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

Purpose5/5

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

The description states precisely what the tool returns: scale, coverage and freshness of the PlaceProfile venue corpus, and immediately disambiguates it from find_venues by describing the countries map as coverage metadata rather than venue results. An agent knows this is a corpus-metadata call, not a search or lookup.

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

Usage Guidelines4/5

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

It gives an explicit decision rule tying this tool to find_venues: check whether a country is present in the countries map before interpreting an empty find_venues result as no-coverage rather than no-venues. It also flags the call as FREE, which signals cheapness. It stops short of an explicit 'call this first / call this when' instruction or naming other siblings.

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