Skip to main content
Glama

Truo

Check in

check_in
Read-only

Use this when the household greets Truo or opens a conversation without a question of their own, for example "Hi Truo". It returns what Truo would offer them now, if anything: three starter questions for a household that has not asked yet, or this week's brief. Make that offer briefly, or greet them if there is none. It reads none of their accounts or transactions. Do not call it when they have asked a question of their own: answer that instead.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
offerNoTrue when Truo has an offer for the household now.
instructionNoWhat to say: the offer, or a plain greeting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered; the description reinforces it with the concrete claim that it reads none of their accounts or transactions. It also discloses the branching return content and instructs the agent to make the offer briefly or just greet when there is none, which is genuine behavioral context beyond the annotations. The only gap is that it doesn't quantify cost or latency, which is minor here.

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?

It is front-loaded with the trigger condition, then the return behavior, then the negative routing rule, so an agent can act after the first sentence. It is slightly longer than necessary — the closing "Do not call it when..." partially restates the opening condition — but no sentence is filler.

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?

With zero parameters, a full output schema, and annotations covering safety and openness, the description supplies exactly the missing piece: when to invoke it and how to present the result. An agent has everything needed to call it correctly.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies no inputs are needed to trigger the behavior.

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 states a concrete trigger and outcome: on a greeting or question-free conversation open, it returns "what Truo would offer them now" — starter questions or this week's brief. That is a specific verb-plus-resource behavior an agent can distinguish from data-retrieval siblings like weekly_brief or list_transactions.

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 both sides of the routing decision: call it when the household greets Truo or opens a conversation without a question of their own (with an example), and explicitly do not call it when they have asked a question — answer that instead. Nothing is left to inference.

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