Skip to main content
Glama

Store the access audit

record_access

Store what the access audit found: one entry per area (repo, hosting, gsc, bing, gmail, reddit, x, social, github, tracking, assets, marketplace) with green, amber or red, what you saw, the one action that turns it green, and facts the plan reads (accountAgeDays, karma, framework). With merge: true, only the areas given are replaced and the rest carry over from the latest audit (a routine that checked one area again, like /shipfound:social). Free. The plan is built only from the latest audit.

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": {
      "areas": "<areas>"
    },
    "name": "record_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNo
areasYes
mergeNo
clientNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / areas / items / properties / id / enum
      Previous value: -[
      -  "repo",
      -  "hosting",
      -  "gsc",
      -  "bing",
      -  "gmail",
      -  "reddit",
      -  "x",
      -  "github",
      -  "tracking",
      -  "assets",
      -  "marketplace"
      -]New value: +[
      +  "repo",
      +  "hosting",
      +  "gsc",
      +  "bing",
      +  "gmail",
      +  "reddit",
      +  "x",
      +  "social",
      +  "github",
      +  "tracking",
      +  "assets",
      +  "marketplace"
      +]
    • changedInput schema / properties / areas / maxItems
      Previous value: -11New value: +12
    • addedInput schema / properties / merge
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare a non-read, non-destructive, closed-world write, and the description adds real context beyond that: merge semantics (partial replacement with carry-over from the latest audit), the fact that the plan consumes only the latest audit, and cost ("Free"). It stops short of stating explicitly that a non-merge call replaces the entire prior audit, which the agent must infer by contrast.

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?

The write payload is front-loaded and the merge caveat follows, so the structure matches reading order. Sentences are long and parenthetical-heavy, but each clause (area list, status vocabulary, fix semantics, facts keys, merge behavior, plan dependency, cost) carries distinct information.

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 nested-object mutation with no output schema and no schema descriptions, the definition covers the payload shape, the merge/replace model, and the downstream consumer (plan). The remaining gaps — the `repo` and `client` parameters and the explicit full-replacement behavior when merge is omitted — are real but secondary.

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?

Schema description coverage is 0%, so the description has to carry the load, and it does for the two most important parameters: `areas` is broken down into id/status (green, amber, red)/detail ("what you saw")/fix ("the one action that turns it green")/facts (with example keys accountAgeDays, karma, framework), and `merge` is explained behaviorally. The top-level `repo` object and `client` string are never mentioned, leaving two of four parameters undocumented.

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 opens with a specific verb and resource ("Store what the access audit found") and enumerates the area IDs and the per-entry payload, so an agent knows exactly what gets persisted. It does not name the sibling `access` tool as the read counterpart, so differentiation is only implied via "the plan is built only from the latest audit".

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?

It gives one genuinely useful conditional: "With merge: true, only the areas given are replaced ... (a routine that checked one area again, like /shipfound:social)", which tells the agent when the merge mode applies. There is no explicit statement of when to use this tool versus `access` or `plan`, and no guidance on when merge should be false beyond the default.

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