Skip to main content
Glama
dreamforgestudiollc

EMET

by dreamforgestudiollc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

emet_member_access_create

Destructive

EMET Member Access: create a one-time code for a new person with read and write access. They paste it on the connect screen instead of the passphrase. This is not EMET Guest Access, and it never makes them the owner.

Instructions

EMET Member Access: create a one-time code for a new person with read and write access. They paste it on the connect screen instead of the passphrase. This is not EMET Guest Access, and it never makes them the owner. Only the owner can create it. Off unless EMET_MEMBER_ACCESS=1.

Input Schema

NameRequiredDescriptionDefault
daysNoDays until the code expires. Default 14.
sourceNoSource tag bound to this member at approval. Exact membership of EMET_SOURCE_TAGS when a registry is set. Required for this member to write documents over HTTP while a registry is set.
display_nameYesName this person will be known by in this store. A name never selects an existing person.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.5
    • addedInput schema / properties / source
      Added value: +{
+  "description": "Source tag bound to this member at approval. Exact membership of EMET_SOURCE_TAGS when a registry is set. Required for this member to write documents over HTTP while a registry is set.",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the mutation profile is covered. The description adds real value beyond that: it is a one-time code granting read/write access, it never confers ownership, it is owner-only, and it is gated behind an environment flag.

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?

Purpose is front-loaded in the first sentence, and the follow-on sentences carry distinct, non-redundant information (connect-screen usage, non-ownership, owner-only, env gate). Slightly long at five sentences but each earns its place.

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 credential-creation tool with no output schema, the description covers who may invoke it, what it grants, and its activation prerequisite. It does not describe what is returned (the code itself) or how approval/expiry interacts, but annotations and schema carry most of the remaining load.

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 display_name, days and source. The description adds no syntax or format detail beyond the schema (only that the code is one-time and expiring), so the baseline 3 applies.

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 (create) and resource (a one-time code for a new person with read/write access), and clarifies it is not Guest Access nor ownership. However it never distinguishes itself from the sibling emet_invite_create, leaving the agent to infer which credential-creation tool to pick.

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 clear preconditions: only the owner can create it, the recipient pastes it on the connect screen instead of the passphrase, and it is off unless EMET_MEMBER_ACCESS=1. It excludes Guest Access but does not explicitly compare against the sibling emet_invite_create.

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

Deploy Server

Other Tools