Skip to main content
Glama

Audit business-notes/ freshness (VIP)

audit_business_notes_freshness
Read-onlyIdempotent

VIP. The monthly Bot Caretaker check. Takes the files in business-notes/ with their last-reviewed dates and says which are fresh, aging, stale or missing, and what to fix first. Without a member token it returns a labeled demo on a sample folder.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audit_business_notes_freshness"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoThe files in business-notes/.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, idempotent, non-destructive, and closed-world, so safety is fully covered elsewhere. The description's genuine addition is the auth fallback: without a member token it returns a labeled demo over a sample folder, which an agent needs to know to interpret results. It does not disclose the scoring thresholds that separate 'fresh' from 'aging' from 'stale', so behavior past the input is only partly transparent.

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?

Four short sentences, front-loaded with the tier marker and purpose before the input and fallback behavior. The leading 'VIP.' is a bare tag whose meaning isn't defined here, a minor bit of unearned text, but overall there is little waste.

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 one-parameter read-only audit with no output schema, the description covers what goes in, what comes back at a high level (four freshness categories plus a fix-first ordering), and the token-less demo path. What's missing is the actual definition of each category and how the ordering is determined, which matters for interpreting results.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains name, content, and last_updated. The description reinforces the role of the last-reviewed dates in the freshness verdict and implies the content field is used to count open [Fill in] lines, but adds no format or default guidance beyond the schema – baseline 3.

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?

Concrete verb-plus-resource: it audits the files in business-notes/ and reports freshness status. The description also names the output buckets (fresh, aging, stale, missing) and the prioritization ('what to fix first'), which tells an agent exactly what the call produces. It does not name any sibling tool, so differentiation is left to the reader.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'The monthly Bot Caretaker check' implies cadence and context of use, and the demo-mode sentence hints at a precondition (member token). But there is no explicit when-not-to-use guidance and no reference to any of the many sibling tools, so an agent must infer that this is the periodic-audit path rather than the diagnostic or setup paths.

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