Meta Council

Set Outreach Sender State

set_outreach_sender_state

Record an owner-observed sender posture and checked time. This does not inspect credentials or verify a provider. Unknown, paused and unsafe remain held; verified alone cannot permit a send. Requires outreach:write.

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": {
      "campaign_id": "<campaign_id>",
      "sender_state": "<sender_state>",
      "sender_state_checked_at": "<sender_state_checked_at>"
    },
    "name": "set_outreach_sender_state"
  }
}

Input Schema

Name	Required	Description	Default
`campaign_id`	Yes
`sender_state`	Yes
`sender_state_checked_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 29, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations only declare the safety profile (not read-only, not destructive, not idempotent), so the description adds real value: it states the tool records observed state rather than verifying, spells out that unknown/paused/unsafe stay held and that 'verified' alone cannot permit a send, and gives the required scope (outreach:write). It omits what the response looks like, but the state-consequence semantics are meaningful beyond annotations.

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?

Four tight clauses, purpose front-loaded, with each subsequent sentence adding a distinct caveat or requirement. No filler.

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 3-parameter mutation tool with no output schema and 0% schema description coverage, the description covers auth and state semantics but leaves the parameter contract under-specified (campaign_id format, complete state vocabulary). Adequate but with clear gaps.

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 coverage is 0%, so the description must carry the load. It maps 'posture' and 'checked time' to two of the three parameters and leaks partial state values (unknown, paused, unsafe, verified), but leaves campaign_id undocumented and does not enumerate the full allowed sender_state set.

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 description gives a specific verb and resource ('Record an owner-observed sender posture and checked time'), making the action legible. However, 'sender posture' is jargon that shadows the parameter name, and there is no differentiation from siblings such as record_outreach_evidence or update_outreach_lead_status.

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

Usage Guidelines3/5

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

It clarifies a boundary ('does not inspect credentials or verify a provider'), which hints at when this is the wrong tool, but it never names an alternative or states a positive when-to-use condition. Usage is implied rather than routed.

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

All Meta Council tools Inspect

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

Need Help?