Skip to main content
Glama

Search a Dataville data source

search_dataville

Query one of Dataville’s data sources (see list_dataville_sources for valid names) with a keyword string. Use it for facts that should come from a real source — company filings, papers, package metadata, nutrition, census figures — rather than from memory. For edgar, a company name or ticker returns its latest filing with that period’s financials and the trailing twelve months to the same date (metadata.financials_ttm); add a form such as "10-K" or "10-Q" to the keywords to pick one.

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": {
      "source": "<source>",
      "keywords": "<keywords>"
    },
    "name": "search_dataville"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesData source name, e.g. 'wikipedia', 'arxiv', 'edgar'
keywordsYesSearch keywords or identifier for the query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose a genuinely useful behavior for edgar — a company name or ticker returns the latest filing with period financials plus trailing-twelve-month data at metadata.financials_ttm — but says nothing about other sources' behavior, invalid-source failure modes, rate limits, or pagination.

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 purpose, then usage rationale, then source-specific detail. Each sentence contributes distinct information — the edgar sentence is dense but every clause (identifier types, TTM field path, form tokens) is actionable.

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

Completeness3/5

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

There is no output schema, so the description must explain what comes back, and it does so only for edgar via metadata.financials_ttm. For wikipedia, arxiv, package metadata, nutrition, or census sources the agent has no idea of the return shape or result volume, which is a meaningful gap for a two-parameter tool with no annotations.

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%, so the baseline is 3, but the description adds real meaning: 'source' is constrained to names enumerated by list_dataville_sources, and 'keywords' accepts a company name, ticker, or an embedded form token like '10-K' to select a filing. That is semantics the schema does not express.

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?

States a specific verb + resource ('Query one of Dataville's data sources ... with a keyword string') and immediately differentiates it from the sibling by routing source-name lookup to list_dataville_sources. An agent can tell exactly what this tool does and what it does not do without opening the schema.

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 says when to use it ('facts that should come from a real source ... rather than from memory') and names the alternative for the prerequisite step (list_dataville_sources for valid names). It also gives a concrete selection rule for the edgar source with an example ('add a form such as "10-K" or "10-Q"'). Only a formal list of when-not-to-use cases is absent.

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.