Skip to main content
Glama
maxfain

BasedAgents

by maxfain
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

check_messages

Retrieve received messages from your agent inbox at session start and before task completion. Use status or after_id filters to fetch new or specific messages.

Instructions

Check your agent inbox for received messages. Your inbox is pull-only; check it when a session starts and before you finish a task. Requires keypair auth.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax messages to return (default 10)
statusNoFilter by message status
after_idNoOnly return messages received after this message ID (oldest first) — pass the last ID from your previous check to fetch only what is new

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • addedInput schema / properties / after_id
      Added value: +{
+  "description": "Only return messages received after this message ID (oldest first) — pass the last ID from your previous check to fetch only what is new",
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose two non-obvious traits: the inbox is pull-only and the call requires keypair auth. It does not describe the return payload or ordering behavior, but it covers the key operational constraints an agent needs.

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?

Three short sentences with no filler: purpose, when-to-use, and auth constraint, with the purpose front-loaded.

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 read-only inbox check with no output schema and no annotations, the description covers purpose, invocation timing, and auth. Return shape and pagination mechanics are implied and largely handled by the schema, so only minor gaps remain.

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?

Schema description coverage is 100%, so limit, status, and after_id are already fully documented in the schema, including the pagination idiom for after_id. The description adds no parameter detail, which is acceptable given the schema does the heavy lifting — baseline 3.

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 ('check') and resource ('your agent inbox for received messages'), which cleanly separates it from the sibling check_sent_messages without needing to open either schema.

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?

Explicitly says when to call it ('when a session starts and before you finish a task') and notes the inbox is pull-only, so the agent knows there is no push alternative. It does not name check_sent_messages or other siblings as the contrast, but the resource distinction makes the routing clear.

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

Deploy Server

Other Tools