Skip to main content
Glama

Brain Scanner

by io.github.kevin-lozada-santos
OverviewDiscussionsAdmin

set_editor_preference

Idempotent

Request the connected local agent to set editor preference; the server stores only bounded metadata and an attested outcome.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detailsNoOptional bounded metadata using only the listed fields, such as summary, status and referenceIds. Not arbitrary command arguments or source content.
projectIdYesOwned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.
sessionIdNoOwned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.
executionIdNoOwned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.
idempotencyKeyYesCaller-generated retry key. Reuse the same key and identical payload only to retry the same mutation; use a new key for a new action.
expectedVersionNoCurrent version of the target record from its latest read or mutation result. A stale value causes a version conflict; re-read before retrying.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / details / description
      Added value: +"Optional bounded metadata using only the listed fields, such as summary, status and referenceIds. Not arbitrary command arguments or source content."
    • addedInput schema / properties / details / properties / status / description
      Added value: +"Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL."
    • addedInput schema / properties / executionId / description
      Added value: +"Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL."
    • addedInput schema / properties / expectedVersion / description
      Added value: +"Current version of the target record from its latest read or mutation result. A stale value causes a version conflict; re-read before retrying."
    • addedInput schema / properties / idempotencyKey / description
      Added value: +"Caller-generated retry key. Reuse the same key and identical payload only to retry the same mutation; use a new key for a new action."
    • addedInput schema / properties / projectId / description
      Added value: +"Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL."
    • addedInput schema / properties / sessionId / description
      Added value: +"Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL."
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations declare non-readonly, idempotent, non-destructive, closed-world. The description adds genuinely new behavioral context: the operation is a *request* to a connected local agent (implying delegation/possible async outcome) and the server persists only bounded metadata plus an 'attested outcome'. This goes beyond what annotations state.

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?

A single front-loaded sentence that leads with the action. The semicolon clause is slightly dense but still efficient and wastes no words.

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 6-parameter mutation with a nested object and no output schema, the description covers the metadata-storage posture but never explains what an 'editor preference' actually is or where its value is carried — notably the schema exposes no preference-valued field. Adequate given full schema coverage, but the core subject is under-specified.

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 the schema already documents every parameter, including details, projectId, and idempotencyKey. The description's 'bounded metadata' phrase reinforces the details constraint but adds no syntax or field-level meaning beyond the schema.

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?

States a specific verb+resource ('set editor preference') and clarifies the mechanism (a request relayed to the connected local agent) plus the storage posture. It does not, however, tie itself to any sibling or explain how 'editor preference' differs from adjacent editor/layout tools like set_context_layout or open_node_in_editor.

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?

There is no when-to-use, when-not-to-use, prerequisite, or alternative guidance. The reader is left to infer from context when this mutation should be invoked versus other agent/session tools.

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

All Brain Scanner toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources