Skip to main content
Glama

Skillshop

audit_grant_proposal

Review a grant narrative the way a reviewer scores it (paid, metered).

sections: {heading: text}. requirements: {required_sections: [..], word_limits: {heading: n}, total_word_limit: n}. request_amount: dollars requested. Returns findings by level (error/warning/nit): missing sections, word limits, unsourced need data, objectives that are not SMART, outputs posing as outcomes, no measurement plan, vague sustainability, request amount mismatch, vague words, placeholders.

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": {
      "sections": "<sections>"
    },
    "name": "audit_grant_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionsYes
requirementsNo
request_amountNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the cost model ('paid, metered') and the shape of the output taxonomy (error/warning/nit) with example finding categories. It does not state that the operation is read-only/non-mutating, nor any limits on input size or runtime, which is the main remaining gap.

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?

Front-loaded with the one-line purpose, then a dense but readable pass over each parameter and the returned finding levels. Every clause carries information; the terse '..'/'n' shorthand is slightly cryptic but not wasteful.

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?

Complexity is moderate (nested object input, enumerated validation logic), and the description covers inputs and the finding taxonomy; the actual finding object shape is carried by the existing output schema, so it need not repeat it. The absence of any note on mutation safety is the only substantive omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: it gives the shape of 'sections' as {heading: text}, spells out the nested keys of 'requirements' (required_sections, per-heading word_limits, total_word_limit), and gives units for request_amount ('dollars requested'). Only edge semantics for the nullable requirements/request_amount defaults are left unstated, which is minor.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Review a grant narrative the way a reviewer scores it') and then enumerates the exact checks performed (missing sections, non-SMART objectives, outputs posing as outcomes, unsourced need data). That enumeration makes it unmistakable that this audits narrative quality rather than the budget, cleanly separating it from audit_grant_budget.

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 '(paid, metered)' note is a useful cost signal that implies 'use sparingly', and the checks imply when the tool is relevant. But there is no explicit when-to-use or when-not guidance, no statement of prerequisites (e.g. does requirements need to be supplied for section checks to run), and no routing to or from the sibling audit tools.

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