centric-demo

draft_as

Draft outreach to a demo contact in a chosen format: email, text, linkedin, or talking_points. Demonstrates Centric's Draft As feature — the draft is grounded in the contact's brief context. Demo only; nothing is sent or logged.

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": {
      "contact": "<contact>"
    },
    "name": "draft_as"
  }
}

Input Schema

Name	Required	Description	Default
`format`	No	Draft format. Defaults to email.	email
`contact`	Yes	Contact id or name, e.g. 'Isabella Chen'

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedJul 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: 'Demo only; nothing is sent or logged' rules out side effects, and 'grounded in the contact's brief context' explains how the output is produced. It does not say whether the draft is template-based or model-generated, or what the response contains, but the safety profile is unusually explicit for an annotation-free tool.

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?

Three sentences, front-loaded with purpose and formats, then the grounding caveat and the no-side-effect note. 'Demonstrates Centric's Draft As feature' is slightly promotional but earns its place by framing the demo scope.

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 2-parameter demo tool with no output schema, the description covers purpose, formats, grounding source and the absence of side effects. The only real gap is the shape of the returned draft (plain string vs. channel-formatted text), which is mild given the tool's simplicity.

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 both the format enum and contact id/name format are already documented; the description largely restates the enum. The one added signal is that the contact anchors grounding, which the schema does not convey. Baseline 3 applies.

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 (draft outreach) plus the resource (a demo contact) and enumerates the four output formats, which cleanly separates it from the sibling lookup tools (get_contact_profile, list_demo_contacts, brief_me). An agent can pick this tool without opening the schema.

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?

Usage is only implied: the contact parameter suggests the agent should first resolve a contact via list_demo_contacts or get_contact_profile, but no sibling is named and no when-not condition is given. No guidance on what to do if the format is unsupported or the contact is unknown.

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

All centric-demo 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?