Skip to main content
Glama

Count Matching Companies

count-matching-domains
Read-onlyIdempotent

Use when the user asks "how many companies match X?" or before running a discovery query to preview result volume.

Accepts structured company filters including industry, location, size, technology and keyword criteria. Returns the matching company count. Seed domains and semantic search text are not accepted.

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": {
      "filters": "<filters>"
    },
    "name": "count-matching-domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoWhy you are calling this tool, in a few words. No names or emails.
filtersYesFilters for the count endpoint, which does not exclude lead-gen sites by default. REST values: https://docs.discolike.com. Invalid values link docs; negate_* uses positive-field values.
llm_modelNoYour model id, or "unknown".
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
countNo
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • removedOutput schema / description
      Removed value: -"Response for count endpoints."
    • addedOutput schema / properties / _mcp_instructions
      Added value: +{
      +  "description": "Server-issued metadata for this conversation.",
      +  "properties": {
      +    "conversation_id": {
      +      "description": "The server-issued conversation identifier.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • removedOutput schema / properties / count / description
      Removed value: -"Number of records matching the query"
    • changedOutput schema / required
      Previous value: -[
      -  "count"
      -]New value: +[]
  2. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Why you are calling this tool, in a few words. No names or emails.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Your model id, or \"unknown\".",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it is a count-only preview and it rejects seed-domain and semantic-text inputs, which prevents a whole class of malformed calls. It does not mention cost/rate limits or that the count endpoint does not exclude lead-gen sites by default (that caveat lives only in the nested schema).

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 short sentences, front-loaded with the trigger condition, then the accepted filter surface, then the return value, then the exclusions. Nothing is redundant and no sentence restates the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't explain the response shape, and it correctly stops at 'returns the matching company count'. For a fairly complex nested filter object it sets expectations well; the only gap is quiet caveats such as lead-gen inclusion defaulting and the absent explicit alternative tool for the unsupported input modes.

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 already documents every filter, including the geo, state, sub-industry and employee_range nuances. The description only summarises filter families (industry, location, size, technology, keyword) and the negative constraint on seed domains/semantic text — helpful framing, but no meaning added beyond the schema.

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 states a concrete verb and resource — returns a count of companies matching supplied filters — and separates itself from retrieval-style tools by naming its role as a volume preview before a discovery query. It does not name a specific sibling tool outright, so differentiation is at the category level rather than tool-to-tool.

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?

It gives two concrete triggering conditions: a user asking 'how many companies match X?', and a pre-flight check before running a discovery query. It also states a boundary (seed domains and semantic search text are not accepted), which implicitly routes those cases to discovery tools, though no alternative is named explicitly.

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