Skip to main content
Glama

List Magic Reach Messages

list_magic_reach_messages
Read-only

List Magic Reach messages for a managed community. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>"
    },
    "name": "list_magic_reach_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number to return, starting at 1.
pageSizeNoNumber of results per page.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
messageStatusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / pageNo / description
      Added value: +"Page number to return, starting at 1."
    • addedInput schema / properties / pageSize / description
      Added value: +"Number of results per page."
  2. First observed

TDQS

A3.5/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 safety is covered; the description goes beyond them by disclosing an entitlement gate, a mandatory pre-check, and required grace-period/resubscribe messaging before proceeding. It still omits pagination behavior and what a message record contains, which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is correctly front-loaded in the first sentence, but the remainder restates the same access requirement three times ("check business permissions," "Call check_business_tool_access," "never proceed when access is blocked"), spending the whole budget on one idea while leaving the parameters and return shape untouched.

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

Completeness3/5

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

For a read-only, non-destructive list tool with annotations covering the safety profile, the access gating is thorough enough to call it safely. It is incomplete in that nothing explains what is returned per message or how paging behaves, and there is no output schema to fall back on.

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

Parameters2/5

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

The description contributes zero parameter meaning — every sentence is about permission gating. With schema coverage at 75%, three of four params are documented in the schema but messageStatus has no description and no enumerated values, and the description does nothing to compensate for that gap.

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 first sentence gives a specific verb and resource ("List Magic Reach messages") scoped to a managed community, which is enough to separate it from create/delete/send siblings. It does not, however, explicitly distinguish itself from get_magic_reach_message or list_magic_reach_message_links/recipients, so the agent must infer the boundary from the names alone.

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?

The description gives an explicit when-not condition ("FREE businesses cannot use this tool, regardless of individual feature rows") and names a prerequisite tool to call first (check_business_tool_access). What it lacks is routing among read siblings — nothing says when to use this listing versus get_magic_reach_message for a single message.

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