Skip to main content
Glama

evidence

by site.chatgpt.lorh89.the-knowledge-commons
OverviewDiscussionsAdmin

start_trial

Start 10 compact reads without an account or report. Two trials per daily network cohort; reuse existing keys. Returns an agent accessKey and a secret owner management link. Give the management link to the owner; never change contribution settings yourself. Automatic sharing starts OFF. Configure the returned accessKey in your MCP Authorization header and reconnect before authenticated tools; this call cannot configure your client.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
noteYes
accessKeyYes
expiresAtYes
manageUrlYes
manageTokenYes
remainingReadsYes
automaticContributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "accessKey": {
+      "type": "string"
+    },
+    "automaticContribution": {
+      "const": false,
+      "type": "boolean"
+    },
+    "expiresAt": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "manageToken": {
+      "type": "string"
+    },
+    "manageUrl": {
+      "format": "uri",
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "remainingReads": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "id",
+    "accessKey",
+    "manageToken",
+    "manageUrl",
+    "remainingReads",
+    "expiresAt",
+    "automaticContribution",
+    "note"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: the quota (two trials per daily cohort), two distinct secrets with different audiences (agent accessKey vs. secret owner management link), the default sharing state (OFF), a governance caveat ('never change contribution settings yourself'), and the limitation that the call cannot configure the client. This is exactly the behavioral disclosure an agent needs for a mutating, non-idempotent call.

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?

Every sentence carries operational weight — quota, return values, secret handling, reconnect requirement. It is dense and somewhat packed, but nothing reads as filler and the setup facts (quota, return shape) are front-loaded.

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?

Complete for a no-parameter trial-start tool. Return values and the reconnect workflow are explained even though an output schema exists, and the governance constraint is stated. An agent has everything needed to call it and handle the result responsibly.

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?

The tool takes zero parameters, so the baseline is 4 and there is no syntax for the description to compensate for. Schema coverage is 100% with an empty object, so nothing is left under-documented.

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 and resource with precise scope: 'Start 10 compact reads without an account or report.' An agent immediately knows this bootstraps a trial. It does not explicitly name which sibling it complements or replaces (e.g., read_research), so it stops short of full sibling differentiation.

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 concrete usage constraints ('Two trials per daily network cohort; reuse existing keys') and post-call instructions ('Configure the returned accessKey in your MCP Authorization header and reconnect before authenticated tools'). It establishes context clearly but does not explicitly compare against alternative sibling tools an agent might otherwise reach for.

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

All evidence 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