Skip to main content
Glama
Sign In

Arbituro

by com.arbituro
OverviewDiscussionsAdmin

Search a project

search
Read-onlyIdempotent

Search one project's existing work, history and published vault documents. Use it before proposing anything, to find whether the question has already been settled.

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": {
      "project": "<project>",
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSpecific terms to find in this project's existing work and history.
projectYesThe project's key, e.g. FLAIR.
searchScopeNo"all" (default) searches every kind of record. "vault" searches only the project's published, curated documents — its settled positions rather than the history of how work went.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful context about the corpus being searched (existing work, history, published vault documents) but says nothing about result shape, ranking, or limits.

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?

Two sentences with no waste, and the scope of the search is front-loaded before the usage advice. Nothing is repeated or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read-only search with full schema coverage and no output schema, the description supplies enough to select and call it correctly. Only minor gaps remain around what the results look like and how they are ranked.

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 all three parameters, including the all-vs-vault searchScope distinction, are already documented in the schema. The description's wording largely restates the same corpus notion without adding syntax or filtering detail beyond it.

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 opens with a specific verb and resource plus scope: searching one project's existing work, history, and published vault documents. That is much clearer than the bare name 'search', but it does not explicitly separate this tool from siblings like what_happened or job_history, which also surface project history.

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

Usage Guidelines4/5

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

It gives an explicit usage directive: 'Use it before proposing anything, to find whether the question has already been settled.' That tells the agent when to reach for this tool, though it names no alternatives and no when-not condition.

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

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