Skip to main content
Glama

Modem

by dev.modem
OverviewDiscussionsAdmin

Search Modem

search_modem
Read-onlyIdempotent

Answer a natural-language question about your Modem data and get matching rows back. Read-only. It does not run the full Modem agent or spend agent credits. Send a question, or send only the cursor from a previous result to fetch its next page. Topic priority in the rows is an integer: very_low (-100), low (-50), default (0), high (50), very_high (100). Before your first call, read the skill: modem_skills({ name: "search-modem" }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size. When set, the engine pages the result server-side and returns a cursor when more rows exist.
cursorNoOpaque continuation token from a previous response. Fetches the next page of the same result set without re-running the search.
columnsNoRequested row shape — the columns each returned row must carry, validated against them (see the schema field on the result). Without it the engine returns a sensible default shape for the question — consistent for common intents, but not validated or guaranteed; pass this whenever you need a SPECIFIC, validated, and stable shape. A cursor continuation reuses the first page’s columns, so it stays stable regardless.
contextNoWhat the user is trying to accomplish with this search. It does not change the results, so put every filter in question.
questionNoNatural-language data question. Required unless cursor is provided. Returns matching rows without invoking the paid Modem agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "What the user is trying to accomplish with this search. It does not change the results, so put every filter in question.",
+  "maxLength": 1000,
+  "type": "string"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds value beyond them: no agent invocation and no credit spend, reuse of first-page columns on cursor continuations, and the integer encoding of the priority topic in returned rows. The skill-call prerequisite is a behavioral requirement that appears nowhere in the structured fields.

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?

Purpose and read-only status are front-loaded, followed by the pagination contract, the result-interpretation note, and the skill prerequisite. Every sentence carries information an agent needs and none is redundant with the schema.

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 five-parameter, zero-required search tool with no output schema, the description covers invocation modes, paging, result shape validation, and the mandatory skill step. An agent has everything required to call it correctly on the first attempt.

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; the description goes further by clarifying the cursor-only call pattern, the mutually exclusive relationship between question and cursor, and that context does not affect results so all filters must live in question. The priority value mapping is documented here rather than in any parameter.

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 and resource – answer a natural-language question about Modem data and return matching rows – and immediately demarcates itself from the sibling modem_agent_invoke by noting it does not run the full agent or spend credits. An agent can distinguish this from the other search/agent tools without opening a 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?

Explicit when-to-use (send a question) and when-to-use-alternatively (send only the cursor to page), plus a prerequisite (read the modem_skills skill before first call) and the cost-based reason to prefer this over the paid agent path. Nothing is left to inference.

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

All Modem toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources