Skip to main content
Glama

search_companies

Find company records in Copper CRM by searching with a company name. Returns matching results with pagination options for efficient browsing.

Instructions

Search Copper companies by name. Returns matching company records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoCompany name to search
page_sizeNoResults per page (default 20, max 200)
page_numberNoPage number (default 1)

Implementation Reference

  • The handler logic for the 'search_companies' tool.
    async ({ name, page_size, page_number }) => {
      const body = {};
      if (name) body.name = name;
      body.page_size = page_size || 20;
      body.page_number = page_number || 1;
    
      const results = await copperFetch("/companies/search", { method: "POST", body });
      const companies = results.map((c) => ({
        id: c.id,
        name: c.name,
        email_domain: c.email_domain,
        phone_numbers: c.phone_numbers,
        websites: c.websites,
        address: c.address,
      }));
      return jsonResult(companies);
    }
  • server.js:192-199 (registration)
    Registration of the 'search_companies' tool with its schema definition.
    server.tool(
      "search_companies",
      "Search Copper companies by name. Returns matching company records.",
      {
        name: z.string().optional().describe("Company name to search"),
        page_size: z.number().optional().describe("Results per page (default 20, max 200)"),
        page_number: z.number().optional().describe("Page number (default 1)"),
      },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the search action and return type but omits critical details like pagination behavior (implied by parameters but not described), rate limits, authentication needs, error handling, or whether it's read-only. This leaves significant gaps for an agent.

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?

The description is two concise sentences with zero waste. It's front-loaded with the core purpose and efficiently states the outcome. Every word earns its place, making it easy to parse.

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?

Given the tool has no annotations and no output schema, the description is incomplete. It lacks behavioral context (e.g., pagination details, safety profile) and output specifics, which are crucial for a search tool with parameters. The description does not compensate for these gaps adequately.

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 fully documents the three parameters. The description adds no additional meaning beyond implying 'name' is the search key, which is already clear from the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the action ('Search') and target resource ('Copper companies by name'), with the outcome ('Returns matching company records'). It's specific but doesn't differentiate from sibling tools like 'search_people' beyond the resource type, which is implied but not explicit.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, when to prefer this over other search or list tools, or any exclusions. It's a basic functional statement without usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dazanza/copper-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server