Skip to main content
Glama

codebahn

by io.github.codebahn
OverviewDiscussionsAdmin

search

Read-onlyIdempotent

Search across repositories, code, issues, users, and organizations. Action 'all' returns hit counts across types; 'code' and 'repos' return paginated results with type-specific filters.

Input Schema

NameRequiredDescriptionDefault
modeNoSearch mode: exact, union, fuzzy. Only for action=codeexact
pageNoPage number (1-based). Ignored for action=all
limitNoPage size. Ignored for action=all
actionYesSearch scope to queryall
keywordYesSearch query
filenameNoFilter by filename or path. Only for action=code
languageNoFilter by programming language. Only for action=code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / action
      Added value: +{
+  "default": "all",
+  "description": "Search scope to query",
+  "enum": [
+    "all",
+    "code",
+    "repos"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / filename
      Added value: +{
+  "description": "Filter by filename or path. Only for action=code",
+  "type": "string"
+}
    • changedInput schema / properties / keyword / description
      Previous value: -"Search keyword"New value: +"Search query"
    • addedInput schema / properties / language
      Added value: +{
+  "description": "Filter by programming language. Only for action=code",
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 30,
+  "description": "Page size. Ignored for action=all",
+  "type": "number"
+}
    • addedInput schema / properties / mode
      Added value: +{
+  "default": "exact",
+  "description": "Search mode: exact, union, fuzzy. Only for action=code",
+  "type": "string"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "description": "Page number (1-based). Ignored for action=all",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "keyword"
-]New value: +[
+  "action",
+  "keyword"
+]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so the safety profile is covered. The description adds genuinely new behavioral detail: the return shape differs by action ('all' returns aggregate hit counts, the others return paginated result sets), which tells the agent what to expect. It omits any note of rate limiting, which is common for search endpoints.

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 tight sentences with the general scope front-loaded and the action-dependent return behavior immediately after. No filler and nothing repeated from the schema.

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 7-parameter read-only tool with full schema coverage, no output schema, and annotations covering safety, the description supplies the one thing the structured data does not: how results differ per action. The only shortfall is the mismatch between the advertised resource types and the available action values.

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 every parameter including mode, filename, language, page, and limit is already documented with its applicable action. The description only alludes generically to 'type-specific filters' without adding syntax or constraint detail beyond the schema, so the baseline 3 is appropriate.

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 (Search) and enumerates the resources it spans, which is much more informative than the bare name 'search'. However, it claims coverage of issues, users, and organizations while the action enum only exposes 'all', 'code', and 'repos', so the stated scope over-promises relative to what can actually be requested.

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?

The description implicitly guides action selection by explaining that 'all' returns hit counts while 'code'/'repos' return paginated results, which implies 'all' is for discovery and the others for retrieval. It never mentions when to use this tool versus the sibling tools (repos, issues, files, commits), so the routing guidance stops short of explicit alternatives.

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

All codebahn toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources