Skip to main content
Glama
Sign In
agent-bus

agent-bus

by rishabhjava
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

search_sessions

Search across all coding agent session transcripts to find matching session IDs using literal text queries.

Instructions

Full-text search across all agents' session transcripts. Returns matching session ids.

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

Input Schema

NameRequiredDescriptionDefault
agentNo
limitNo
queryYesLiteral text to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description bears full responsibility for revealing behavioral traits. It states it performs a full-text search and returns IDs, but does not disclose read-only nature, performance implications, authentication requirements, or any side effects.

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?

The description is very concise (two sentences) and front-loaded with the key action. No unnecessary words, though additional details could be added without harming conciseness.

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?

Given the lack of an output schema and annotations, the description is insufficiently complete. It does not cover search scope details (e.g., case sensitivity), the role of the 'agent' filter, or what 'full-text' includes. The return type is stated, but more context is needed for effective use.

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 low (33%) meaning only the 'query' parameter has a description. The tool description adds no additional parameter information beyond what is in the schema; it does not explain the 'agent' enum or 'limit' constraints.

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 clearly identifies the tool as a full-text search across all agents' session transcripts and specifies that it returns matching session IDs. This distinguishes it from siblings like list_sessions and read_session, though it could more explicitly differentiate from ask_agent.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention typical use cases, prerequisites, or situations where other tools would be more appropriate.

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

Deploy Server

Other Tools