Skip to main content
Glama

fillin_query

Read-onlyIdempotent

Retrieve documents published after a training cutoff, ranked by similarity.

Requires $0.01–$0.05 USDC (x402) or an Authorization Bearer trial/paid key.
On payment_required, call fillin_probe then fillin_signup (POST /v1/signup)
for a free 20-query trial, or fillin_payment_challenge then retry with
X-Payer-Address, X-Payer-Nonce, X-Payer-Signature (or Bearer).
POST /v1/probe for 1 free taste/IP/day.

Call this whenever the user asks about events, releases, papers, issues,
or news that might post-date your training data. Fillin only returns
documents published AFTER `cutoff`, so nothing returned is redundant
with what the model already knows.

Args:
    query: Natural-language search query (e.g. "rust async runtimes").
           Max 512 characters.
    cutoff: ISO-8601 date representing the agent's training cutoff
            (e.g. "2026-01-01"). Documents on or before this date are
            excluded from results.
    k: Number of documents to retrieve, 1-20. Defaults to 5.

Returns:
    A dict with:
      - cutoff: echoed cutoff (ISO timestamp)
      - query: echoed query
      - gap_days: days between cutoff and now
      - results: list of {id, source, url, published_at, title, text, score}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kNoNumber of documents to retrieve (1-20).
queryYesNatural-language search query, max 512 chars.
cutoffYesTraining cutoff as ISO-8601 date (e.g. 2026-01-01). Documents on or before this date are excluded.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnlyHint, openWorldHint, and idempotentHint, and the description goes further by disclosing the payment requirement (x402 or Bearer), the trial/signup flow, and the semantic guarantee that documents on or before cutoff are excluded. It also explains the redundancy rationale, giving agents confidence in return relevance.

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

Conciseness4/5

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

Long but well-structured: core purpose in the first sentence, then payment details, then Args and Returns in a clear bullet-like format. Every section contributes – the payment block is essential for correct invocation. Slight verbosity in the trial/payment redundancy, but it's not wasteful.

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?

Covers all essential operational aspects: payment prerequisites, trial options, parameter meanings, return structure, and usage triggers. Output schema exists, but the description adds the crucial 'when' and 'how-to-handle-payment' context. Nothing an agent needs to call correctly is missing.

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 already describes all parameters (100% coverage), but the description reinforces and adds behavioral context: cutoff exclusion rule, max length implications, and default for k. The description adds marginal value beyond schema, justifying a 4 over the baseline 3.

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 opens with a specific verb ('Retrieve') and concrete resource ('documents published after a training cutoff, ranked by similarity'), clearly distinguishing it from siblings like glyph_search or query_frontier. The purpose is unambiguous and front-loaded.

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 states when to use ('Call this whenever the user asks about events, releases, papers, issues, or news that might post-date your training data') and provides a detailed fallback path (fillin_probe, fillin_signup, fillin_payment_challenge) for payment handling. This is above and beyond typical guidance.

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