Skip to main content
Glama

Football Atlas

by app.futbolatlas

Answer a question about Football Atlas

answer
Read-onlyIdempotent

Answer a question from the corpus. Returns the matched object's claims with sources and confidence — never an unsourced answer. Use this when the user asked a question in words; use search when you want to see the candidates yourself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionYesThe question to answer, in the words the user asked it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
claimsNo
entityNo
answeredYes
matched_questionNo

TDQS

A4.5/5.0
Behavior4/5

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

Annotations cover read-only and idempotent behavior, and the description adds meaningful context: it never returns an unsourced answer and returns claims with sources and confidence. This goes beyond the annotations and helps set expectations without contradicting them.

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 short sentences, each earning its place: the action, the return guarantee, and the usage guidance. The core purpose is front-loaded, and there is no redundant wording.

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

Completeness5/5

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

For a simple one-parameter tool with full schema coverage, rich annotations, and an output schema, the description is complete. It covers purpose, behavior, return characteristics, and when to choose an alternative.

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?

Schema description coverage is 100%, and the description does not add meaning beyond what the schema already provides for the single 'question' parameter. The baseline of 3 applies because the schema carries the parameter semantics fully.

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 clearly states the verb and resource: it answers a question from the corpus. It also differentiates from the 'search' sibling by emphasizing that it returns a direct answer with sources and confidence, not just candidates.

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

Usage Guidelines5/5

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

Explicitly instructs when to use the tool: when the user asked a question in words. It also names the alternative 'search' and the condition for choosing it, giving the agent clear routing guidance.

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

All Football Atlas toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Every tool targets a distinct retrieval mode: answer for direct questions, search for candidate discovery, get_entity for a single object, get_related for graph neighbours, get_topic for tag browsing, get_latest for freshness, get_sources for citations, and get_overview for corpus-level context. The descriptions also explicitly contrast each tool with the alternatives that might be confused with it.

Naming Consistency4/5

The majority of tools follow a clear get_<noun> pattern (get_entity, get_topic, get_sources, get_overview, get_related, get_latest), and all names are lowercase snake_case. The two query actions, answer and search, break the get_ prefix pattern slightly, but they are intentionally different entry-point verbs rather than resource fetches.

Tool Count5/5

Eight tools is well within the ideal range for a knowledge-graph query server. Each tool covers a distinct aspect of corpus exploration without feeling redundant or bloated.

Completeness5/5

The server covers the full read-only workflow for a football knowledge atlas: corpus overview, freshness, full-text search, direct question answering, entity lookup, relation traversal, topic browsing, and source verification. Gaps like create/update/delete are not needed for this domain, and the descriptions deliberately handle misses with near-miss suggestions.

Resources