Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Search companies

search_companies
Read-only

Find vendors and makers on CommunityCAD by querying company listings with pagination.

Instructions

Search companies (vendors and makers) on CommunityCAD.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-data profile is covered. Beyond that the description adds only the entity types returned; it says nothing about matching semantics (substring vs fuzzy), what an empty query returns, or how pagination behaves past the 25-result cap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, which is good. But brevity here comes from under-specification rather than efficiency: there was room for a matching-behavior or paging clause at no structural cost.

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?

With no output schema, three undocumented parameters, and no usage guidance, an agent cannot tell what the result objects look like or how to page through them. A search tool in a catalog of 21+ siblings needs more than an entity-type gloss to be callable with confidence.

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% – the three parameters are bare names with types and bounds. The description does not explain what query matches against (company name, aliases, product lines) or that limit/offset page through results, so it 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?

The description gives a specific verb and resource ('Search companies') and adds scope with '(vendors and makers)', which tells an agent what kind of entities come back. It does not distinguish itself from the sibling get_company or the other search_* tools, so sibling differentiation is left to the caller.

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?

There is no when-to-use guidance: nothing says whether to pick this over get_company for a known name, or over search_models/search_datasheet when hunting for a maker. The only implied usage is 'searching', which the name already conveys.

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