Skip to main content
Glama

Inspect Signature

inspect_signature
Idempotent

Verify an active artifact's code-signing identity, hashes, authorities, requirements, entitlements, hardened-runtime state, and command provenance to confirm authenticity and runtime trust.

Instructions

Inspect the active artifact's code-signing identity, hashes, authorities, requirements, entitlements, hardened-runtime state, and exact command provenance.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare non-destructive, idempotent, open-world behavior, so the bar is lower; the description adds the useful scoping detail that results are tied to the currently active artifact and lists what categories of data come back. However, it does not address the tension between the word 'inspect' and readOnlyHint=false (it may shell out to signing tools), nor permissions, cost, or what happens for an unsigned artifact.

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?

A single sentence with the action and subject front-loaded, followed by an enumerated payload list; nothing is redundant and every listed item tells the agent whether this tool answers its question.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no parameters, the description carries the full burden of explaining results, and it does so by enumerating the disclosed fields. Gaps remain: unsigned/adhoc-signed artifact behavior, whether the artifact must be selected beforehand, and any platform applicability are unstated.

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?

Zero parameters, so the schema has nothing to explain and the baseline is 4. The description still contributes meaningful semantics by making explicit that the target is the *active* artifact rather than an identified one — an implicit selection dependency an agent must satisfy before calling.

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?

Specific verb ('Inspect') plus a precise resource ('the active artifact's code-signing identity') and an enumerated scope of what is disclosed: hashes, authorities, requirements, entitlements, hardened-runtime state, command provenance. This clearly separates it from general binary/artifact readers like inspect_macho or inspect_artifact, but the description never explicitly says those siblings won't surface signing data, so differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use, when-not-to-use, or prerequisite guidance beyond the phrase 'active artifact'. The agent is left to infer that an artifact must first be selected and that this is the tool for signing/notarization questions rather than general metadata questions.

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