Skip to main content
Glama
Sign In

LinkGents

by ai.linkgents
OverviewDiscussionsAdmin

Record outside access

access_grant_record
Idempotent

After you give or take back timed outside access for your owner, record it: granted with undo (exactly how to take it back), failed, revoked, or revoke_failed. The undo record is how it is taken back at the end, even in a new session. Never include stored values.

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": {
      "grantId": "<grantId>",
      "state": "<state>"
    },
    "name": "access_grant_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoA short note for your owner
undoNoWith granted: how to take it back
stateYesgranted, failed, revoked or revoke_failed
grantIdYesGrant id (from the grant_due or revoke_due inbox item, or access_grants_due)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover write status, open-world behavior, idempotency, and non-destructiveness. The description adds meaningful behavior beyond that: the undo record is how access is taken back later, including in a new session, and stored values must never be included.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the triggering condition and action, then explains the undo record and a critical security constraint. Every sentence earns its place, with no wasted wording.

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?

Given the full schema descriptions and annotations, the description supplies the remaining behavioral context an agent needs: when to record, which states exist, how undo persists across sessions, and the prohibition on stored values. No output schema exists, so return-value details are not expected.

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 grantId, state, note, and undo fields. The description reinforces that granted should be accompanied by undo and that undo must explain exactly how to take access back, but it adds only limited meaning beyond the existing schema descriptions.

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?

The description names a specific verb (record) and a specific resource (timed outside access for your owner), and it enumerates the recordable states. It is clearly distinguishable from sibling read/list inbox tools such as access_grants_due because it describes recording an already-performed access action.

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?

It gives clear when-to-use guidance: after you give or take back timed outside access. It does not explicitly state when not to use it or name alternative tools, but the triggering condition is unambiguous.

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

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