Skip to main content
Glama
ShellFrameAI

AgentSecure Community

Official
by ShellFrameAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

agentsecure.identity

Look up or register agent identities in the local Community Mesh store, returning metadata or agent lists and writing an audit event on registration.

Instructions

Look up or register identities in the local Community Mesh store. By default, agent_id returns exists plus that identity's metadata (or exists=false if unknown); omitting agent_id returns an agents array sorted by ID. Set register=true with a non-empty agent_id to create or overwrite its record and write an audit event; returns the saved identity. Registration replaces rather than merges metadata. Identity labels, trust_level, and allowed_scopes do not authenticate callers or grant permissions. Example: {"agent_id": "backend-agent"}.

Input Schema

NameRequiredDescriptionDefault
nameNoDisplay name for registration; defaults to agent_id. Ignored on lookup.
teamNoTeam label for registration; defaults to empty. Used when counting approvals assigned to this team; ignored on lookup.
typeNoAgent classification for registration; defaults to coding_agent. Metadata only; ignored on lookup.
ownerNoOwner label for registration; defaults to empty. Does not verify ownership; ignored on lookup.
agent_idNoLocal Mesh ID to look up or register. Omit/empty to list identities when register=false; non-empty required when register=true. Not inferred from the environment or authenticated.
registerNoDefaults to false (lookup only). True creates or overwrites the agent_id record using the metadata below, including defaults for omitted fields.
workspaceNoWorkspace label for registration; defaults to local. Does not select a filesystem directory; ignored on lookup.
trust_levelNoTrust label for registration; defaults to local. Metadata only, not a security boundary; ignored on lookup.
allowed_scopesNoScope labels to store at registration; defaults to []. Informational only, not enforced by Mesh policy; ignored on lookup.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / agent_id / description
      Added value: +"Local Mesh ID to look up or register. Omit/empty to list identities when register=false; non-empty required when register=true. Not inferred from the environment or authenticated."
    • addedInput schema / properties / allowed_scopes / description
      Added value: +"Scope labels to store at registration; defaults to []. Informational only, not enforced by Mesh policy; ignored on lookup."
    • addedInput schema / properties / name / description
      Added value: +"Display name for registration; defaults to agent_id. Ignored on lookup."
    • addedInput schema / properties / owner / description
      Added value: +"Owner label for registration; defaults to empty. Does not verify ownership; ignored on lookup."
    • addedInput schema / properties / register / description
      Added value: +"Defaults to false (lookup only). True creates or overwrites the agent_id record using the metadata below, including defaults for omitted fields."
    • addedInput schema / properties / team / description
      Added value: +"Team label for registration; defaults to empty. Used when counting approvals assigned to this team; ignored on lookup."
    • addedInput schema / properties / trust_level / description
      Added value: +"Trust label for registration; defaults to local. Metadata only, not a security boundary; ignored on lookup."
    • addedInput schema / properties / type / description
      Added value: +"Agent classification for registration; defaults to coding_agent. Metadata only; ignored on lookup."
    • addedInput schema / properties / workspace / description
      Added value: +"Workspace label for registration; defaults to local. Does not select a filesystem directory; ignored on lookup."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well: it discloses that lookup returns exists=false for unknown IDs, that the agents array is sorted by ID, that registration overwrites rather than merges, that an audit event is written, and that labels/scopes are not security boundaries. These are exactly the mutation and side-effect facts an agent needs.

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 purpose, then the default behavior, then the mutation mode, then a caveat, then an example. Every sentence carries distinct information and nothing is repeated from the schema verbatim.

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?

A 9-parameter tool with no annotations and no output schema, yet the description covers both return shapes (exists + metadata, agents array, saved identity), overwrite semantics, and the non-security nature of the stored metadata. Nothing an agent needs to call it correctly is missing.

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 conditional semantics beyond the field docs: omitting agent_id lists identities, non-empty agent_id is required for register, and defaults are applied to omitted fields on overwrite. The worked example reinforces the minimal lookup call.

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 opens with a specific verb pair and resource: 'Look up or register identities in the local Community Mesh store.' It also distinguishes the two operational modes by argument shape, so an agent can tell what the tool does without opening the schema.

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 explicitly states when each mode applies: default lookup when agent_id is supplied, listing when agent_id is omitted, and write when register=true with a non-empty agent_id. There are no sibling tools with overlapping identity duties, so no explicit alternates are needed, but it also doesn't mention prerequisites or error handling.

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

This server cannot be deployed

Other Tools