Skip to main content
Glama

SOTA2 — AI Solution Rankings

Look up an AI company by name

search_companies
Read-onlyIdempotent

Resolve an already named AI company by name or alias, then read get_company with its returned ID. The default company_name mode also accepts concise literal capability keywords for broader unranked candidates; such matches do not prove industry fit. For a business problem or a new vendor shortlist, use find_ai_companies. Existing callers can still use intent business_need here with a full English workflow; it returns the same task-scoped company candidates as find_ai_companies. Preserve coverage gaps and unknown facts.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRequested number of individual result rows (1–50): top 2 corresponds to limit 2. Also the page size for continuation requests.
queryYesWith business_need: the full English problem, desired work, industry and constraints, preserving all channels and phone/booking requirements. Translate other languages without dropping requirements. With company_name: an exact known name/alias, or concise literal capability keywords for unranked text matches.
intentNoUse business_need for a full English problem/workflow when finding new providers. company_name preserves existing exact-name/alias or concise literal capability-keyword lookup.company_name

Output Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / intent
      Added value: +{
      +  "default": "company_name",
      +  "description": "Use business_need for a full English problem/workflow when finding new providers. company_name preserves existing exact-name/alias or concise literal capability-keyword lookup.",
      +  "enum": [
      +    "company_name",
      +    "business_need"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / query / description
      Added value: +"With business_need: the full English problem, desired work, industry and constraints, preserving all channels and phone/booking requirements. Translate other languages without dropping requirements. With company_name: an exact known name/alias, or concise literal capability keywords for unranked text matches."
    • changedInput schema / properties / query / maxLength
      Previous value: -120New value: +500
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior, and the description adds meaningful caveats beyond them: capability-keyword matches are broader and unranked and do not prove industry fit, business_need returns task-scoped candidates like find_ai_companies, and coverage gaps should be preserved. There is no contradiction with annotations.

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 front-loaded with the primary action and follow-up step, then gives mode-specific guidance and the alternative sibling tool. It is mostly efficient, though it carries several dense clauses and a legacy-caller note that make it slightly longer than strictly necessary.

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?

Given the full schema coverage, rich annotations, and an output schema, the description supplies the remaining invocation context an agent needs: the two intent modes, the follow-up get_company flow, sibling routing, and the caveat that keyword matches are unranked. Nothing critical for correct selection or invocation is missing.

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 description coverage is 100%, so the baseline is 3. The description still adds useful semantic context about the two intent modes: company_name for exact names, aliases, or concise literal keywords, and business_need for a full English workflow with task-scoped results. It does not add much about limit, but the schema already documents that parameter well.

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 states a specific verb and resource: resolve an already named AI company by name or alias, then read get_company with its returned ID. It also distinguishes the tool from siblings find_ai_companies and get_company by clarifying the lookup versus discovery versus detail-retrieval roles.

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

Usage Guidelines5/5

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

It explicitly says when to use this tool versus find_ai_companies: use find_ai_companies for a business problem or new vendor shortlist, while this tool is for an already named company or concise literal capability keywords. It also explains the legacy business_need intent path, leaving little ambiguity about alternatives.

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