Scribase

Set a flag

flags.set

Creates or changes one flag of this branch's environment; apps read the change within a minute with no redeploy. Reversible: set it back the same way. Scope: projects: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": {
      "key": "<key>",
      "enabled": "<enabled>"
    },
    "name": "flags.set"
  }
}

Input Schema

Name	Required	Description
`key`	Yes	Flag key: a letter, then lowercase letters, digits and underscores
`value`	No	Optional text value the app reads
`branch`	No	Branch (environment) id. Optional: defaults to `production`.
`enabled`	Yes	On (true) or off (false)
`project_id`	No	Project id. Optional: defaults to the project used last in this session, or the only one.
`description`	No	Optional note for people
`organization_id`	No	Organization id. Optional: defaults to the token's organization, or the only one you belong to.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing propagation latency (apps read the change within a minute, no redeploy) and the required scope (projects:write), both of which affect planning. The reversibility statement is useful but the description does not say what happens to an existing flag's value/description when they are omitted — a meaningful gap for an upsert. Note the mild tension with idempotentHint=false, since writing the same key/value twice converges to the same state, but this is not a direct contradiction.

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?

Three short, front-loaded sentences: what it does, how the change propagates and is undone, then the required scope. No filler and nothing buried.

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 7-parameter mutation with full schema coverage and existing annotations, the description supplies the operationally important extras (latency, auth scope, reversibility). It would be complete with a note on partial-update behavior when value/description are omitted, but nothing essential is missing for correct invocation.

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 100%, so all seven parameters, including the branch, project, and organization defaults, are already documented in the schema. The description only adds the notion that the write targets "this branch's environment," without elaborating on key format, value semantics, or defaulting behavior. Baseline 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 and resource ("Creates or changes one flag of this branch's environment") with scope made explicit (branch/environment level). This clearly separates it from the sibling flags.list and from unrelated setters like branches.masking.set.

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 upsert framing ("creates or changes") tells the agent this single tool covers both new and existing flags, and the reversibility note ("set it back the same way") gives guidance on undoing. It stops short of naming when not to use it or pointing to flags.list for reading.

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

All Scribase 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?