Skip to main content
Glama

past.dev

by dev.past
OverviewDiscussionsAdmin

Create an MCP access link

create_mcp_access_link

Mints an access link to a project's MCP server for one identity: an MCP URL whose secret is the credential, so a client connects with it and every call runs as that identity, with no sign-in. The server must be on. identity names an identity the project already holds; with newIdentity: true it is created here, with traits (for example {"kind": "agent"}), which decide the audiences it is in. The answer carries the link: show it to the person once, and never paste it anywhere but back to them, since it is not recoverable here afterwards. Mirrors Build › MCP server › Create access link; needs project Admin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
traitsNoTraits for a new identity, as key and value. Only with newIdentity: true.
projectNoThe project's slug, exactly as list_projects returned it. Omit it only when the organization has one live project.
identityYesThe identity the link is for, as the project's identity directory names it.
expiresAtNoWhen the link stops working, as an ISO 8601 date or time in the future; omitted, it never does.
newIdentityNoCreate the identity with this link. Refused when the project already holds it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / expiresAt / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / project / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / traits / additionalProperties / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / traits / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (which only say non-read-only, non-destructive, non-idempotent), it discloses the crucial traits of the artifact: the link embeds a credential and cannot be recovered here afterwards, so it must be shown once and not pasted elsewhere. It also adds the auth requirement (project Admin) and the server-must-be-on precondition, none of which the annotations carry.

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?

Front-loaded with the purpose in the first clause, then layered constraints and the one-time-secret warning, then the UI mirror and permission note. Dense but every sentence carries actionable information; no filler.

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?

There is no output schema, and the description compensates by saying exactly what the answer carries (the link) and that it is not retrievable later. Combined with the server and Admin preconditions, an agent has everything needed to call and handle the result correctly.

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 schema already documents all five parameters; the description nonetheless adds meaning, notably that traits decide which audiences the identity joins, plus a concrete example ({"kind": "agent"}) and the newIdentity/identity interaction. It mostly reinforces rather than extends the schema, so it sits just above the baseline.

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: mints an access link to a project's MCP server for one identity, with the link's nature (MCP URL whose secret is the credential) spelled out. It is clearly distinguishable from create_api_key and get_mcp_server, and the identity-scoped, no-sign-in behavior is explicit.

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 prerequisites and context: the server must be on, the identity must already exist in the project (or be made via newIdentity: true), and the caller needs project Admin. It implies but never names the sibling that turns the server on (enable_mcp_server) or the general-purpose alternative create_api_key, so routing is left partly to inference.

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

All past.dev toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources