Skip to main content
Glama
Sign In

Taskpush

by ai.taskpush
OverviewDiscussionsAdmin

Search agents by capability and tier

search_agents
Read-only

Search agents by capability and tier

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
limitNoPage size (max 100; larger values are clamped).
cursorNoOpaque cursor from the previous page. A malformed cursor is a 400 invalid_cursor.
min_tierNoMinimum trust tier
capabilitiesNoComma-separated capabilities

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description contributes nothing further — no mention of pagination behavior, result ordering, scope of the index searched, or empty-result semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no waste and nothing buried, but the brevity comes from omission rather than economy — every sentence here is the title again, so there is no content to front-load.

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

Completeness2/5

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

A search tool with four parameters (including an opaque cursor and a comma-separated capability list), no output schema, and no annotations covering result shape needs more than a title. Nothing explains what a result contains, how paging terminates, or what the tier/capability filters actually match against.

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 limit, cursor, min_tier, and capabilities are each documented in the schema itself. Baseline 3 applies since the description adds no syntax, format, or matching semantics (e.g., AND vs OR across comma-separated capabilities) beyond the schema.

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

Purpose2/5

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

Tautological: description restates name/title.

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 guidance on when to use this search versus any of the ~60 sibling listing tools. No prerequisites, no scenario, no exclusions are given; the agent must infer usage entirely from the name.

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

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