Skip to main content
Glama

glyph_search

Read-onlyIdempotent

Same as fillin_query, but returns the result pieces rendered as photo glyph image(s) — dense, vision-readable pages — followed by a JSON citation index ({n, source, url, title, published_at, page}).

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.

Read the image(s) directly with your vision capability; use the citation
index to attribute or follow up. Glyphs are for comprehension and
fact-extraction, not verbatim quotes (vision models paraphrase) — open the
url for exact text. Billed at the flat /query rate; rendering is free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kNoNumber of documents to retrieve (1-12).
tierNoGlyph density tier: 6x | 10x | 15x.10x
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
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

The description goes well beyond the annotations (readOnlyHint, openWorldHint, idempotentHint) by disclosing the billing model (flat /query rate, rendering free), the payment requirement, the need to read images with vision capability, the caveat that glyphs are for comprehension not verbatim quotes, and the instruction to open URLs for exact text. This is rich behavioral context that annotations alone do not provide.

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?

The description is dense but well-structured: it front-loads the core purpose, then covers output format, auth/payment, and usage caveats. Every sentence carries information, though the payment flow details are somewhat lengthy and could arguably be trimmed. Still, it earns a 4 for efficiency and organization.

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?

The description is complete for an agent to invoke the tool correctly: it explains the output format, the payment/auth prerequisites, the error-handling flow, and the limitations of the glyph output. The output schema exists, so return values are documented elsewhere. Nothing critical is missing.

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%, so the schema already documents all four parameters (query, cutoff, k, tier) with descriptions. The description adds context about the output format (photo glyph images + citation index) but does not add new parameter-level semantics beyond what the schema provides. Baseline 3 is appropriate.

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 tool's function: it performs the same search as fillin_query but returns results as photo glyph images with a JSON citation index. It explicitly distinguishes itself from the sibling tool fillin_query, making the purpose unambiguous.

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?

The description provides explicit guidance on when to use this tool (when you want vision-readable glyph pages) and contrasts it with fillin_query. It also details the payment/auth requirements and the exact fallback flow (fillin_probe, fillin_signup, fillin_payment_challenge) for handling payment_required errors, which is comprehensive usage 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