Skip to main content
Glama

get_policy

Retrieve the company's accounts-payable policy to learn approval rules and thresholds before processing invoices.

Instructions

The company's accounts-payable policy. Read it first: the rules and their thresholds differ between companies.

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": "get_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full load. It signals a safe read ('Read it first') and that the returned rules are company-specific, which is genuinely useful context for interpreting later results. It says nothing about the length, structure, or volatility of the policy document, leaving an agent unsure what to expect from the response.

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?

Two short sentences with zero waste: the identity of the resource comes first, then the imperative to call it and the reason why. Nothing is repeated and nothing could be cut without losing guidance.

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 zero-parameter, no-output-schema document fetch, the description covers what it returns, why it matters, and when to call it. The only gap is the absence of any hint about the shape or scope of the policy content the agent will receive.

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

Parameters4/5

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

The tool takes no parameters, so there is nothing for the description to explain and the baseline of 4 applies. No misleading parameter hints are given.

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 names the specific resource ('the company's accounts-payable policy') and characterizes its contents as 'rules and their thresholds,' which distinguishes it from the data-fetching siblings like get_invoice and get_vendor. The retrieval verb is only implied by 'Read it first' rather than stated, so it falls just short of a clean verb+resource statement.

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

Usage Guidelines4/5

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

'Read it first' gives explicit ordering guidance that an agent can act on before calling invoice/PO tools, and the reason is supplied (thresholds differ between companies). It does not state when the tool can be skipped or name an alternative source, which keeps it below a 5.

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