SpecStream

Set a member's role and limit

put_project_member

Destructive

Sets a person's role in a project, editor or viewer, and their own monthly spending limit.

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": {
      "account_id": "<account_id>",
      "role": "<role>",
      "project_id": "<project_id>"
    },
    "name": "put_project_member"
  }
}

Input Schema

Name	Required	Description	Default
`role`	Yes
`account_id`	Yes
`project_id`	Yes
`monthly_spend_cap_cents`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

B3/5.0

Behavior3/5

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

The annotations already declare this as a non-read-only, destructive mutation, so the description does not need to establish that baseline. It adds some useful context by saying the role and per-person spending limit are set, but it does not explain what existing values are overwritten, what permissions are required, or what happens if the optional spend cap is omitted.

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?

The description is a single front-loaded sentence with no wasted wording. The role values and spend-limit behavior are stated immediately, although the overall brevity is insufficient for the tool's complexity.

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

Completeness2/5

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

This is a destructive four-parameter mutation with no output schema and 0% schema description coverage. The description omits permissions, overwrite behavior, member-existence requirements, and semantics for two of the four parameters, leaving significant gaps for an agent to infer.

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?

Schema description coverage is 0% for four parameters, so the description must carry the burden. It mentions the role (editor or viewer) and a monthly spending limit, but it does not explain account_id or project_id, does not state that the spend cap is expressed in cents, and does not mention its optional default of 0.

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 uses a specific verb and resource: it sets a person's role in a project and their monthly spending limit. It is clear enough to distinguish this from invite_project_member and revoke_project_member, though it does not explicitly name or contrast those siblings.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, prerequisites, or alternatives. It does not say whether the member must already exist, how this differs from invite_project_member, or when revoke_project_member would be appropriate instead.

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

All SpecStream 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.