Skip to main content
Glama

Digital Footprint Score

digital-footprint-score
Read-onlyIdempotent

Use when the user asks about a company's online presence, web authority, digital maturity, or company size proxy. The score (1-800) is a reliable indicator of company scale and activity.

Proprietary score computed from web infrastructure, social signals, and activity indicators across 80M+ sites. Returns the score with a parameter breakdown showing how each component contributed.

Input parameters: domain. Definitions in input schema.

Available fields for the 'fields' parameter: domain, score, parameters, first_event. Field details: https://docs.discolike.com. score: Final calculated score (0-999, higher is better)

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": "digital-footprint-score"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOutput fields to include in response
contextNoWhy you are calling this tool, in a few words. No names or emails.
filtersYesInput filters for getting digital footprint score.
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
scoreNo
domainNo
warningsNo
parametersNo
first_eventNo
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / additionalProperties
      Removed value: -true
    • 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"
      +  },
      +  "first_event": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "null"
      +      }
      +    ]
      +  },
      +  "parameters": {
      +    "properties": {
      +      "base_score": {
      +        "anyOf": [
      +          {
      +            "type": "number"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "expiration_penalty": {
      +        "anyOf": [
      +          {
      +            "type": "number"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "growth_boost": {
      +        "anyOf": [
      +          {
      +            "type": "number"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "lookback_360": {
      +        "anyOf": [
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "lookback_720": {
      +        "anyOf": [
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "recency_multiplier": {
      +        "anyOf": [
      +          {
      +            "type": "number"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      }
      +    },
      +    "required": [],
      +    "type": "object"
      +  },
      +  "score": {
      +    "type": "integer"
      +  },
      +  "warnings": {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  }
      +}
    • 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.8/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, non-destructive read, so the bar is lower, yet the description still adds real context: the score's provenance (web infrastructure, social signals, activity across 80M+ sites) and the fact that a parameter breakdown is returned showing component contributions. It omits latency, coverage limits, and what happens for domains with insufficient data.

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 when-to-use and what-it-computes sentences are front-loaded and earn their place, but the tail is bloated with 'domain. Definitions in input schema.', a bare docs URL, and a field list that largely duplicates the output schema. The inconsistent score range appears in the same block, muddying rather than tightening the structure.

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 need not detail return values, and annotations fully cover the safety profile; the description fills the remaining gaps with intent triggers and computation provenance. The unresolved 1-800 vs 0-999 discrepancy and the undefined 'parameters'/'first_event' fields keep it from being complete.

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 coverage is 100%, so the schema already documents all five parameters and the baseline is 3. The description adds a field enumeration and a definition for 'score', but 'domain. Definitions in input schema.' is filler and 'parameters'/'first_event' are named without explanation. It also contradicts itself on the value range, stating 1-800 up front and 0-999 in the field note, which leaves the agent unsure how to interpret the result.

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 names the resource (a proprietary digital footprint score) and what it is computed from (web infrastructure, social signals, activity across 80M+ sites), so an agent knows it returns a numeric authority/scale metric for a domain rather than a profile or metrics table. It does not explicitly contrast itself with plausible siblings such as business-profile or growth-metrics, so it stops short of a 5.

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?

The opening 'Use when the user asks about a company's online presence, web authority, digital maturity, or company size proxy' gives concrete triggering intents. There are no exclusions or named alternatives, so the agent must still infer whether business-profile or growth-metrics is the better fit.

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