Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Get a company

get_company
Read-only

Retrieve a company's public profile and its associated models by slug or ID, with pagination options for browsing results.

Instructions

A company's public profile and its models.

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": {
      "slug": "<slug>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe company's slug (from search_companies or a model) or id.
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

C2.3/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 profile is covered. Beyond that the description adds only that the response includes the company's models, and says nothing about pagination of that embedded collection, rate limits, or what happens with an invalid slug.

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

Conciseness2/5

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

Short, but it is a single incomplete fragment rather than a front-loaded sentence with a verb, and its brevity reflects under-specification rather than efficiency. There is no wasted wording because there is almost no wording.

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 tool with three parameters, no output schema, and a paginated sub-collection (models), the description is too thin to tell an agent what it will get back or how pagination behaves. It lacks the essentials needed to call it confidently relative to its complexity.

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 coverage is 33%: only 'slug' is documented (helpfully pointing to search_companies or a model), while 'limit' and 'offset' are bare numbers with defaults but no stated effect. The description does not compensate at all, leaving it unclear that limit/offset paginate the embedded models list rather than the company itself.

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

Purpose3/5

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

The fragment states the resource ('A company's public profile') and hints at related data ('its models'), which lets an agent infer a read of company details. However it is a noun phrase with no verb and no scope statement, so it only vaguely conveys the action compared with siblings like get_model or search_companies.

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 description gives no when-to-use guidance, no prerequisites, and never distinguishes this from search_companies (which is the natural lookup path to obtain a slug) or get_model. An agent must infer selection 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.