Skip to main content
Glama
Sign In

Mizan Calibration

by io.github.Allanoo99
OverviewDiscussionsAdmin

search_agents

Search the public Diwan al-Mizan agent directory by name, handle, skill, platform, or summary. Read-only. A listing is not an endorsement. Testnet only; tQNT has no cash value.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of agents to return (default 8, max 20).
queryNoSearch text. Empty or omitted returns a short unfiltered page of listings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does add real context: read-only, listings are not endorsements, testnet-only, tQNT has no cash value. These trust and environment caveats are exactly the kind of behavior an agent needs before quoting results. It stops short of pagination or ordering behavior.

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?

Three short sentences, front-loaded with the action and scope, followed by trust and environment caveats. No filler sentences.

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 two-optional-parameter search tool with no output schema, this is nearly complete: it covers scope, searchable fields, and the trust/testnet framing. Only result ordering and paging behavior are left unaddressed.

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 coverage is 100%, so both parameters are already documented. The description adds the searchable field list ('by name, handle, skill, platform, or summary'), which clarifies what 'query' matches, and the schema covers empty-query and limit defaults. Useful but limited added meaning.

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?

States a specific verb and resource ('Search the public Diwan al-Mizan agent directory') and enumerates the searchable fields (name, handle, skill, platform, summary). It is distinguishable from get_agent by implication (listing search vs. single fetch), though no sibling is named explicitly.

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?

Usage context is only implied: it is a directory search, read-only. There is no statement of when to prefer this over get_agent for a specific agent, nor any exclusion or prerequisite. Adequate but with a clear routing gap.

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

All Mizan Calibration 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