Skip to main content
Glama

Codenation

Search tools

search_tools
Read-onlyIdempotent

Search the Codenation index of developer and SaaS tools. Every word of query must match the tool's name, tags, tagline, category or description; results are ranked by relevance. Filter by category, tag or pricing. Returns short records (slug, name, tagline, category, pricing, tags, website, codenation_url) and the total number of matches. Call get_tool with a slug for the full record and checked price. With no query, lists tools alphabetically.

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

Input Schema

NameRequiredDescriptionDefault
tagNoExact tag, e.g. "open-source" or "llm". Optional.
limitNoResults per page.
queryNoKeywords, e.g. "self-hosted analytics" or "auth". Optional.
offsetNoResults to skip, for paging.
pricingNoPricing model. Optional.
categoryNoCategory slug. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, yet the description adds genuine behavioral detail beyond them: conjunctive matching ("Every word of `query` must match"), relevance ranking, the explicit field list returned, the total match count, and the alphabetical ordering when query is empty. That is exactly the kind of return-shape and ranking semantics annotations cannot carry.

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?

Four dense sentences, front-loaded with purpose, then matching semantics, then filters, then the sibling hand-off and the empty-query behavior. No sentence is filler and nothing is buried.

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?

There is no output schema, and the description compensates by naming the returned fields (slug, name, tagline, category, pricing, tags, website, codenation_url) plus the total match count, so an agent knows what it gets back and why to follow up with get_tool. For a six-parameter, all-optional search tool this is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema lacks: query is conjunctive across name/tags/tagline/category/description, and category/tag/pricing act as narrowing filters. It does not explain limit/offset paging beyond what the schema's own descriptions already say, which keeps it below 5.

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?

States a specific verb and resource ("Search the Codenation index of developer and SaaS tools") and immediately scopes it against the sibling that retrieves full records: "Call get_tool with a slug for the full record and checked price." An agent can distinguish this from get_tool, list_categories, and list_collections without opening any schema.

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?

Gives clear routing: use this for short records, then call get_tool with a slug for the full record and checked price, and it explains the no-query fallback ("lists tools alphabetically"). It does not mention browsing category/tag vocabularies via list_categories or list_collections, which is a plausible alternative path when the agent doesn't know a filter value.

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