Context Studios MCP

List Roles

list_roles

Read-only

List the buyer/user roles Context Studios addresses (e.g. founder, CTO, marketing manager), with name, one-line summary, and canonical + Markdown-twin URLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_roles"
  }
}

Input Schema

Name	Required	Description	Default
`locale`	No	Preferred content locale.	en
`responseFormat`	No	Response shape. Use v2 for agent-friendly {success,data,meta,error}; legacy remains available for older clients.	legacy

Output Schema

Name	Required	Description
`data`	No	Structured result payload. Present for responseFormat='v2' tools.
`meta`	No	Result metadata such as count, locale fallback, cache scope, or response format.
`count`	No	Number of returned records for list and search tools.
`error`	No	Human-readable error message when success is false.
`success`	No	Whether the tool call completed successfully.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 25, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and a closed world, and the description adds useful context by naming the role scope and the exact return contents (name, one-line summary, canonical + Markdown-twin URLs). It does not contradict annotations and provides enough behavioral context for a simple read-only list.

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?

A single, front-loaded sentence that states the action, scope, examples, and output fields with no wasted words. It is compact and immediately scannable.

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 simple read-only list with an output schema and annotations, the description covers the core scope and output sufficiently. Missing explicit sibling routing and minor behavioral details like ordering/pagination are small gaps, not critical ones.

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%: both locale and responseFormat have enums, defaults, examples, and descriptions. The tool description adds no parameter-specific meaning, so the schema carries the burden and the baseline score of 3 is appropriate.

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 ('List') and a clear resource ('buyer/user roles Context Studios addresses') with concrete examples (founder, CTO, marketing manager) and output details. This distinguishes it from get_role and other list_* siblings without needing to open 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?

The description implies use when an agent wants an overview of buyer/user roles, but it does not explicitly say when to prefer it over alternatives like get_role or other list_* tools. No exclusions or when-not-to-use guidance is provided.

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

All Context Studios MCP 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?