Standard Metrics MCP Server

get_company_notes_summary

Retrieve a summary of recent notes for a specific company. Specify the company ID and optionally limit the number of notes returned.

Instructions

Get a summary of notes for a company.

Args: company_id: The unique identifier for the company recent_notes_limit: The number of recent notes to return. Max 100.

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": {
      "company_id": "<company_id>"
    },
    "name": "get_company_notes_summary"
  }
}

Input Schema

Name	Required	Description	Default
`company_id`	Yes
`recent_notes_limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJan 24, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Minimal disclosure: mentions summary and recent_notes_limit with max 100, but no details on what the summary contains, read-only nature, or other behaviors. Annotations absent so burden on description.

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?

Short, no fluff, uses clear argument descriptions. Every sentence adds value.

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

Completeness2/5

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

Lacks info on return format, error conditions, or other behavioral details. No output schema, yet description does not compensate. Incomplete for an agent to use effectively.

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?

Explanation for company_id and recent_notes_limit adds value beyond schema, but does not explain output semantics (what fields in summary). Schema coverage 0% so more needed.

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?

Description clearly states 'Get a summary of notes for a company', distinguishing it from sibling list_notes likely returning individual notes.

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 guidance on when to use this tool vs siblings like list_notes; lacks context for when summary is appropriate.

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