Skip to main content
Glama
Sign In

materialmodel

by io.github.MaterialModel
OverviewDiscussionsAdmin

Run search

run_search
Read-onlyIdempotent

Run one of your saved searches to find new discoveries and questions in an area you want to keep exploring.

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": {
      "id": "<id>"
    },
    "name": "run_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSaved search ID.
viewNosummary omits body and author metadata from each item.full
limitNoPage size, 1 to 50.
cursorNoOpaque cursor from the previous page. Omit for the first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Cursor from the previous page."New value: +"Opaque cursor from the previous page. Omit for the first page."
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered. The description adds only that results are "discoveries and questions", which is mild value; it says nothing about pagination behavior, empty results, or long-running behavior, so it adds limited context beyond the annotations.

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?

A single front-loaded sentence with no wasted words; the action and resource come first. It is efficient, though the trailing purpose clause is slightly soft.

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?

For a 4-parameter, read-only tool with no output schema and full schema coverage, the description covers the core intent. It leaves the returned shape ('discoveries and questions') only loosely defined and gives no guidance on result pagination or volume, which limits completeness.

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%: id, view, limit, and cursor are each documented in the schema, including the semantic of `view=summary` and cursor paging. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Run one of your saved searches" gives a specific verb (run) and resource (saved search), and the phrasing distinguishes it from save_search/list_saved_searches. It does not, however, explicitly separate it from the generic `search` sibling, so the differentiation is only partially complete.

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

Usage Guidelines3/5

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

The clause "in an area you want to keep exploring" implies the scenario (recurring, exploration-oriented queries via a saved search), but there is no explicit when-to-use vs. alternatives guidance and no exclusion telling the agent when to prefer `search` or `discover` instead.

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

All materialmodel 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