Skip to main content
Glama

Growth Metrics

growth-metrics
Read-onlyIdempotent

Use when the user asks whether a company is growing, expanding, hiring, or wants to see trends over time. Single-domain lookup.

Returns 5 quarters of historical growth data including employee count changes, digital footprint score trends, and subdomain expansion — modeled from ~20 public web signals, not self-reported data.

Note: Response includes dynamic quarterly fields (score_YYYYQX, subdomains_YYYYQX) in addition to the base fields.

Input parameters: domain. Definitions in input schema.

Available fields: domain, score_growth_3m, subdomain_growth_3m. Field details: https://docs.discolike.com.

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": "growth-metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
contextNoWhy you are calling this tool, in a few words. No names or emails.
filtersYesInput filters for getting growth metrics.
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
domainNo
score_growth_3mNo
_mcp_instructionsNoServer-issued metadata for this conversation.
subdomain_growth_3mNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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"
      +}
    • addedOutput schema / properties
      Added value: +{
      +  "_mcp_instructions": {
      +    "description": "Server-issued metadata for this conversation.",
      +    "properties": {
      +      "conversation_id": {
      +        "description": "The server-issued conversation identifier.",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "domain": {
      +    "type": "string"
      +  },
      +  "score_growth_3m": {
      +    "anyOf": [
      +      {
      +        "type": "number"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  },
      +  "subdomain_growth_3m": {
      +    "anyOf": [
      +      {
      +        "type": "number"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  }
      +}
    • addedOutput schema / required
      Added 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

A3.9/5.0
Behavior4/5

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

The annotations already declare this as a read-only, idempotent, non-destructive, closed-world lookup. Beyond those annotations, the description adds useful behavioral context: it returns five quarters of history, is modeled from roughly 20 public web signals rather than self-reported data, and includes dynamic quarterly fields. It does not discuss freshness, limits, or error behavior, so it stops short of a 5.

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 usage guidance is front-loaded and the return behavior is explained in a compact block. Some lines, such as 'Input parameters: domain. Definitions in input schema,' are redundant with the schema, but the overall structure is easy to scan and does not ramble.

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?

For a read-only lookup with annotations and an output schema, the description covers the main call context, return scope, data provenance, and dynamic field caveat. It does not need to explain return values in detail because an output schema exists, though it could say more about how to interpret the growth fields.

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 80%, so the schema already carries most parameter meaning. The description mentions the domain input and lists available fields, but it does not explain domain formatting, field selection behavior, or the auxiliary parameters. This is adequate but mostly relies on 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 clearly states that this tool returns historical growth data for a company, including employee counts, digital footprint trends, and subdomain expansion. It is specific about the resource and output, but it does not explicitly distinguish itself from adjacent tools such as digital-footprint-score or business-profile.

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 a clear usage condition: use when the user asks whether a company is growing, expanding, hiring, or wants trends over time. It also says 'Single-domain lookup,' which implies a scope boundary, but it does not name alternative tools or state when not to use this one.

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