Skip to main content
Glama
Sign In

AI Design Blueprint

by com.aidesignblueprint
OverviewDiscussionsAdmin

Add Evidence Note

me.add_evidence

Authenticated: append a free-text evidence note to a specific stage in the caller's active course. Notes record concrete implementation observations, decisions, or artefacts that demonstrate progress through a Blueprint principle (e.g. how a delegation boundary was implemented, what approval flow was chosen and why). Persisted as UserStageEvidence rows scoped to (user_id, course_slug, stage_id). WHEN TO CALL: AFTER the user has articulated something concrete they have built, observed, or decided, not to capture intent or speculation. Pair with me.coaching_context to close evidence gaps. WHEN NOT TO CALL: to log every conversation turn; to record planning, ideas, or todos; on behalf of another user; without the user's awareness (they should know their progress is being recorded). BEHAVIOR: write-only, single insert. Auth: Bearer (any plan). Data at rest in the UK. Notes are visible only to the owning user and are surfaced on me.learning_path / me.coaching_context. Confirms the stage_id + course_slug pair in the response so the user can see which stage was credited.

Input Schema

NameRequiredDescriptionDefault
noteYesEvidence note to append to the delegation boundary notes for this stage.
stage_idYesID of the stage to append the evidence note to.
course_slugYesSlug of the course the stage belongs to (e.g. 'agentic-fundamentals').

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "add_evidence_noteDictOutput",
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "ErrorBody": {
-      "description": "The body of `error_payload(code, message, details)` returns.",
-      "properties": {
-        "code": {
-          "title": "Code",
-          "type": "string"
-        },
-        "details": {
-          "additionalProperties": true,
-          "title": "Details",
-          "type": "object"
-        },
-        "message": {
-          "title": "Message",
-          "type": "string"
-        }
-      },
-      "title": "ErrorBody",
-      "type": "object"
-    }
-  },
-  "properties": {
-    "error": {
-      "$ref": "#/$defs/ErrorBody",
-      "default": null
-    },
-    "evidence_id": {
-      "default": null,
-      "title": "Evidence Id",
-      "type": "string"
-    },
-    "guidance": {
-      "default": null,
-      "title": "Guidance",
-      "type": "string"
-    },
-    "status": {
-      "default": null,
-      "title": "Status",
-      "type": "string"
-    }
-  },
-  "title": "MeAddEvidenceResponse",
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "ErrorBody": {
+      "description": "The body of `error_payload(code, message, details)` returns.",
+      "properties": {
+        "code": {
+          "title": "Code",
+          "type": "string"
+        },
+        "details": {
+          "additionalProperties": true,
+          "title": "Details",
+          "type": "object"
+        },
+        "message": {
+          "title": "Message",
+          "type": "string"
+        }
+      },
+      "title": "ErrorBody",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "error": {
+      "$ref": "#/$defs/ErrorBody",
+      "default": null
+    },
+    "evidence_id": {
+      "default": null,
+      "title": "Evidence Id",
+      "type": "string"
+    },
+    "guidance": {
+      "default": null,
+      "title": "Guidance",
+      "type": "string"
+    },
+    "status": {
+      "default": null,
+      "title": "Status",
+      "type": "string"
+    }
+  },
+  "title": "MeAddEvidenceResponse",
+  "type": "object"
+}
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only give the generic hints; the description adds material context: write-only single insert, Bearer token of any plan, UK data residency, visibility limited to the owning user, and confirmation of the crediting stage in the response. It also discloses the consent expectation (user should know progress is recorded) that annotations cannot convey.

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 core action and scoping, then structured labels (WHEN TO CALL / WHEN NOT TO CALL / BEHAVIOR) make it skimmable. It is long and slightly repetitive about visibility and pairing tools, which keeps it from a 5.

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

Completeness5/5

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

For a three-parameter write tool with an output schema, everything an agent needs is present: purpose, trigger conditions, exclusions, auth, write semantics, visibility and the response confirmation. No gaps remain that would cause a mis-call.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it clarifies that the note captures concrete implementation observations, decisions or artefacts tied to a Blueprint principle, and that the tuple (user_id, course_slug, stage_id) scopes persistence and is echoed back. It does not explain formats or boundaries for stage_id/course_slug beyond the schema.

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 — 'append a free-text evidence note to a specific stage in the caller's active course' — and explains what the note contains. It also names the siblings that surface the data (me.learning_path, me.coaching_context), so it is distinguishable from other me.* tools.

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

Usage Guidelines5/5

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

Explicit WHEN TO CALL (after the user articulates something concrete they built/observed/decided) and WHEN NOT TO CALL (no logging every turn, no planning/todos, not on behalf of another user, not without awareness). It also names me.coaching_context as the pairing tool for closing evidence gaps.

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

All AI Design Blueprint toolsInspect
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