Skip to main content
Glama

Prepare the system in a private Merron workspace

merron_prepare_workspace

Save this AI system to Merron so the user can build an evidence pack from it: the name, a description, the answers the user confirmed and the file/line findings from merron_scan_project. Returns a private single-use link, valid 7 days; the user signs in, the system opens prefilled and Merron guides them through connecting the code, confirming the answers and creating the pack. Ask the user first and tell them what will be saved. Never include code excerpts, secrets or personal data; findings carry only paths, line numbers and codes. Give the user the link exactly as returned.

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": {
      "userAgreed": "<userAgreed>",
      "system": "<system>"
    },
    "name": "merron_prepare_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
systemYes
userAgreedYesTrue only after the user agrees to save these details to Merron.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / system / additionalProperties
      Removed value: -false
    • addedInput schema / properties / system / properties / facts / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / properties / system / properties / findings / items / additionalProperties
      Removed value: -false
  2. Changed1 schema field changed
    • changedInput schema / properties / system / properties / facts / additionalProperties / anyOf
      Previous value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "enum": [
      -      "provider",
      -      "deployer",
      -      "both"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "enum": [
      +      "provider",
      +      "deployer",
      +      "both"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "enum": [
      +      "high_risk",
      +      "not_high_risk_6_3",
      +      "not_stated"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare the mutation/safety profile; the description adds substantive behavior the annotations cannot: a private single-use link valid 7 days, a sign-in step, a prefilled workspace, and the guided flow that follows. It also discloses hard data-handling limits — no code excerpts, secrets or personal data, findings limited to paths, line numbers and codes.

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?

Front-loaded with the action and payoff, followed by return value, then the consent and privacy constraints. Dense but every sentence carries operational value; only the final 'Give the user the link exactly as returned' leans toward generic instruction.

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?

No output schema exists, and the description compensates by explaining what comes back (a private 7-day single-use link) and what the user experiences after signing in. For a two-parameter nested write tool with an irreversible-external-effect profile, this is nearly complete; only the fact-key vocabulary inside 'facts' remains unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 50% schema coverage and a nested object, the description carries real weight: it maps 'system' to name, description, confirmed answers ('facts') and file/line findings from merron_scan_project, and constrains findings to paths, line numbers and codes. It does not describe the meaning of individual fact keys or the 60-item findings cap, which the schema enforces silently.

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 — 'Save this AI system to Merron' — plus the downstream goal (build an evidence pack). It also names its upstream sibling merron_scan_project as the source of findings, so an agent can place it in the workflow 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 Guidelines4/5

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

Gives an explicit precondition: 'Ask the user first and tell them what will be saved', and ties its input to merron_scan_project output. It does not explicitly say when not to call it (e.g. when scanning has not yet been run), leaving that sequencing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources