Skip to main content
Glama

Truo

Weekly brief: not now

decline_weekly_brief

Call this only when you offered this week's brief and the household said no. Truo notes the no inside Truo and does not offer the brief again for 7 days. The household can still ask for the brief at any time, and then you call weekly_brief as usual. It reads none of their accounts or transactions. Do not call it for any other reason.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNo
notedNoTrue when Truo saved the no. False only where the tool is not available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the refusal is recorded inside Truo, that the brief is suppressed for 7 days, that the household can still request it manually, and that no accounts or transactions are read. This adds real state-change and data-access context the readOnlyHint=false / destructiveHint=false flags alone do not convey.

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?

The gating condition comes first, followed by the effect, the exception, and the prohibition. Four short sentences, each carrying distinct information, with no redundancy against the title or annotations.

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

Completeness5/5

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

An output schema exists, so return values need not be explained, and the description fully covers trigger, side effect, duration, and scope of data access for a zero-parameter tool. Nothing an agent needs to call it correctly is missing.

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 zero parameters, so the baseline is 4 and there is no parameter meaning the description could add. Schema coverage is 100% and additionalProperties is false, leaving nothing ambiguous to document.

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?

The description names a specific action (recording the household's refusal of this week's brief) and its effect, not merely a restatement of the name. It explicitly separates itself from the sibling weekly_brief by explaining that a later request goes through that tool instead.

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

Usage Guidelines5/5

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

It gives a precise trigger ('only when you offered this week's brief and the household said no'), an explicit exclusion ('Do not call it for any other reason'), and the alternative path (call weekly_brief if the household later asks). No inference is required.

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