Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

Search HelpMyAgent APIs

search_apis
Read-onlyIdempotent

Find published HelpMyAgent capabilities matching a natural-language task or intent without executing or charging for a paid call. Returns matching endpoint descriptors with pricing, coverage, usage guidance and documentation. Optional category, country and max_price filters narrow the catalogue search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesDescribe the desired outcome or agent task in natural language; matching uses endpoint names, descriptions, tags, usage guidance and example queries.
countryNoOptional ISO 3166-1 alpha-2 country code, for example FR; matching is case-insensitive and restricts results to APIs declaring that coverage.
categoryNoOptional exact published category slug; when supplied, only APIs in that category are considered.
max_priceNoOptional inclusive maximum advertised unit price per call; APIs priced above this value are excluded.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
apisYesMatching API descriptors including endpoint, pricing, coverage, usage guidance and documentation links.
countYesNumber of published APIs matching the supplied discovery criteria.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Optional exact category slug returned by list_categories; when supplied, only APIs in that category are considered."New value: +"Optional exact published category slug; when supplied, only APIs in that category are considered."
  2. Changed2 schema fields changed
    • addedOutput schema / properties / apis / description
      Added value: +"Matching API descriptors including endpoint, pricing, coverage, usage guidance and documentation links."
    • addedOutput schema / properties / count / description
      Added value: +"Number of published APIs matching the supplied discovery criteria."
  3. Changed4 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Optional HelpMyAgent API category."New value: +"Optional exact category slug returned by list_categories; when supplied, only APIs in that category are considered."
    • changedInput schema / properties / country / description
      Previous value: -"Optional ISO 3166-1 alpha-2 country code, for example FR."New value: +"Optional ISO 3166-1 alpha-2 country code, for example FR; matching is case-insensitive and restricts results to APIs declaring that coverage."
    • changedInput schema / properties / max_price / description
      Previous value: -"Optional maximum price per call in the API currency."New value: +"Optional inclusive maximum advertised unit price per call; APIs priced above this value are excluded."
    • changedInput schema / properties / query / description
      Previous value: -"Describe the task or intent to match against the published HelpMyAgent API catalogue."New value: +"Describe the desired outcome or agent task in natural language; matching uses endpoint names, descriptions, tags, usage guidance and example queries."
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds meaningful behavior beyond them by explicitly stating that this tool does not execute or charge for a paid call and returns descriptors rather than live API results. This is important safety-relevant context for an agent deciding whether to invoke the tool.

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 sentences with no filler: the purpose and non-execution guarantee are front-loaded, the return content is specified, and the filters are listed compactly. Every sentence contributes essential information.

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

Completeness5/5

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

For a catalogue-search tool with fully documented parameters and an output schema, the description covers everything needed to invoke it correctly: natural-language querying, non-execution, returned descriptor content, and narrowing filters. No critical invocation detail is missing.

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 the schema already documents all four parameters. The description only mentions the query and the three optional filters at a high level, adding no syntax, matching details, or exact-value semantics beyond what the schema provides. Baseline 3 is appropriate.

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

Purpose5/5

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

The description opens with a specific verb-resource pair, 'Find published HelpMyAgent capabilities,' and adds the critical qualifier 'without executing or charging for a paid call,' distinguishing it from execution-oriented endpoints and from related discovery tools like describe_api. It clearly states the return content: matching endpoint descriptors with pricing, coverage, usage guidance, and documentation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly establishes when to use the tool: when an agent has a natural-language task or intent and wants to discover published APIs without executing a call. It does not explicitly name alternatives such as describe_api or list_categories or state when those would be preferred, so it stops short of full alternative routing.

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

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