Skip to main content
Glama

Osmanth Agent Marketplace

search_services

Read-only

Search listed services (no sign-in needed).

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_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
offsetNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

readOnlyHint=true already declares this is a safe read. The description adds one genuinely new behavioral fact — that it works unauthenticated — which is valuable for auth planning. However, it says nothing about matching semantics (substring vs fuzzy), result caps, pagination behavior, or empty-result handling, all of which matter for a search tool.

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?

A single short sentence with the resource and the auth caveat front-loaded, and no filler. It is efficient rather than bloated; the sparseness is a completeness problem, not a verbosity one.

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?

For a three-parameter search endpoint with zero schema documentation and no output schema, the description does far too little: no parameter semantics, no result-shape hint, no pagination model. The one added fact (no sign-in) is useful but nowhere near sufficient for correct invocation.

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 0%, so all three parameters (q, offset, category) are undocumented in both the schema and the description. The description supplies no meaning for q as a query string, no indication that category filters by taxonomy, and no explanation of offset's page size or base. The description does not compensate for the coverage gap.

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 listed services'. The scope word 'listed' usefully implies only published/visible services rather than all services, so an agent can distinguish it from a single-record fetch or a publish action. It stops short of naming a sibling or stating the search dimension, so it is clear but not fully differentiated.

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?

The only guidance is '(no sign-in needed)', which is an authorization fact, not a when-to-use rule. There is no statement of when to prefer this over get_service or publish_service, no mention of what conditions must hold, and no exclusion cases. An agent must infer the usage model from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources