Skip to main content
Glama

search_papers

Find relevant papers by meaning within a run's corpus, using the same embedding model as S3.

Instructions

Semantic search over the run's papers (same embedding model as S3).

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": {
      "run_id": "<run_id>",
      "query": "<query>"
    },
    "name": "search_papers"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
top_kNo
run_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and largely does not meet it: it never states that the operation is read-only, what ranking or ordering the results come back in, or how the run scope interacts with missing runs. The one genuine disclosure is that the embedding model matches S3, which tells the agent scores are comparable to that analysis, but that is a small fraction of what a mutation-free retrieval tool should disclose.

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 short sentence that is front-loaded with the core operation and adds one qualifying detail, with no filler. It is efficient, though the brevity is partly under-specification rather than disciplined compression.

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?

An output schema exists, so return-value shape does not need explaining, and the run scoping is conveyed. However, for a three-parameter tool with zero schema coverage and no annotations, the definition leaves query semantics, top_k behavior, and result ordering to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, and the description only indirectly explains run_id via the phrase "the run's papers." It says nothing about query semantics (natural language vs keyword) or what top_k counts or caps, leaving the agent to guess at both.

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?

The description pairs a specific verb ("semantic search") with a specific resource ("the run's papers"), so an agent knows this is vector-similarity retrieval scoped to one run rather than a general paper lookup. It stops short of naming any sibling to contrast with, so the differentiation is only partial.

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

Usage Guidelines2/5

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

There is no statement of when to use this instead of other retrieval tools such as answer_question or run_s3_analysis. The parenthetical about the shared embedding model hints at a relationship to S3 analysis but never converts that into a usage rule or exclusion.

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