Skip to main content
Glama

ramadasmr-networkcalc-mcp

by ai.smithery
OverviewDiscussionsAdmin

spf_lookup

Fetch SPF info for a given domain or host

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / domain / description
      Added value: +"Domain to look up"
    • removedInput schema / properties / domain / title
      Removed value: -"Domain"
    • removedInput schema / title
      Removed value: -"spf_lookupArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "spf_lookupOutput",
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It fails to specify what 'SPF info' entails (raw TXT record vs parsed policy), error handling when no SPF record exists, or whether it follows include/redirect mechanisms. It only states the action without explaining the result.

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?

Extremely concise at 8 words. Single sentence with no filler. The description is front-loaded with the verb and immediately identifies the resource type. No structural improvements possible without adding missing content.

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

Completeness3/5

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

For a single-parameter lookup tool, the description covers the basic intent but remains minimal. Given the absence of an output schema, the description should ideally specify what the return value contains (record string, validation result, etc.). It meets minimum viability but leaves operational gaps.

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% (the 'domain' parameter is documented in the schema). The description mentions 'domain or host' which aligns with the parameter, but adds no additional semantic value regarding accepted formats (e.g., whether subdomains are handled differently) beyond what the schema already provides. Baseline 3 is appropriate.

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 tool 'Fetch[es] SPF info' using a specific verb and resource type. It specifies the scope ('for a given domain or host'), implicitly distinguishing it from general DNS lookups (sibling dns_lookup) by focusing specifically on SPF records rather than generic record types.

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 provides no guidance on when to use this tool versus alternatives. Given the sibling dns_lookup tool could theoretically retrieve TXT records (which contain SPF data), the description should clarify when to use this specialized tool versus the general DNS lookup.

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

All ramadasmr-networkcalc-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources