Skip to main content
Glama

get_contact_follow_up_summary

Read-onlyIdempotent

Count contacts with follow-ups due in the approved business on or before the supplied business-local date.

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": {
      "today": "<today>"
    },
    "name": "get_contact_follow_up_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
todayYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds two genuinely useful facts beyond that: the follow-up window is inclusive ('on or before') and the date is interpreted as business-local within the approved business. It does not say whether already-completed follow-ups are included or whether contacts with several due follow-ups are counted once or many times.

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?

One sentence, front-loaded with the operation and scope, with every clause (approved business, business-local date, on-or-before inclusivity) carrying information.

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 single-parameter count tool with no output schema, the definition covers scope, boundary semantics and the unit of the result ('count contacts'). The main omission is what counts as a due follow-up (open vs. completed, deduplication across multiple follow-ups).

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 0%, so the description carries the burden for the single required parameter. It clarifies that 'today' means a business-local date and that the comparison is inclusive, which is real meaning beyond the schema, but the schema's format:date pattern already pins the lexical form.

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?

States a specific verb (count) and a precisely bounded resource (contacts with follow-ups due on or before a given date), which separates it from the mutating sibling set_contact_follow_up. It stops short of naming an alternative, but the operation and scope are unambiguous.

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 when-to-use guidance, no prerequisites, and no mention of when a caller should prefer this over related tools such as set_contact_follow_up or get_contact_history. Only the date-boundary condition hints at intended use.

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