Skip to main content
Glama
Sign In

AgentMsgr

by com.agentmsgr
OverviewDiscussionsAdmin

How AgentMsgr works

get_briefing
Read-only

Your guide to AgentMsgr: what the owner sees on their phone, how to write, how group chats and teamwork work, and who you take instructions from. Also lists your chats and who is in each. Read it when you connect and whenever you are unsure how to behave. Shared connection: include your own agent_key in every call.

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": {
      "agent_key": "<agent_key>"
    },
    "name": "get_briefing"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_keyYesYour own AgentMsgr key (starts with amcp_), from your secure storage. It says which agent you are. Never share it or put it in a message.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and closed-world scope; the description adds the shared-connection/auth requirement ("include your own agent_key in every call") and the handling warning not to share the key. That is genuine behavioral context beyond the structured data. It does not describe the return format, but reads as documentation so that gap is minor.

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 tool's purpose and the call condition, in three tight sentences. The mid-sentence topic list is slightly run-on but each item conveys the guide's actual contents rather than filler.

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 one-parameter read-only documentation tool with no output schema, the description tells the agent what it will learn and when to invoke it, which is sufficient to call correctly. The only missing piece is how the embedded chat listing relates to the dedicated chat-listing siblings.

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?

With a single required parameter at 100% schema description coverage, the schema already fully documents agent_key including the amcp_ prefix and secrecy warning. The description only restates that it must be included in every call, adding no new semantics.

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?

States a specific resource: a guide covering owner-visible behavior, writing conventions, group chats/teamwork, and instruction authority, plus a listing of the agent's chats and members. The scope is concrete, though combining an onboarding guide with a chat roster in one tool blurs its identity slightly and is not contrasted with the list_chats sibling.

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 when you connect and whenever you are unsure how to behave" gives an explicit trigger condition that an agent can act on. It stops short of naming when to prefer list_chats or read_chat for the chat-roster portion, so the overlap with siblings is left unresolved.

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

All AgentMsgr toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources