Skip to main content
Glama

Create install session

create_install_session
Idempotent

Create a 15-minute signed download for one granted Ready skill or collection. Select target=my_draft with skill_slug to test only the authenticated author's unreviewed Draft.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
targetNo
skill_slugNo
collection_slugNo

Output Schema

NameRequiredDescriptionDefault
dataYes
viewYes
workspaceNo
generated_atYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description adds useful context: the artifact is signed and expires after 15 minutes, and only 'granted' skills/collections qualify. However it does not say what authorization is needed for draft testing or what happens when the grant is missing.

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?

Two tight sentences, front-loaded with the core behavior and the expiry detail, then the draft-testing variant. No filler, though the second sentence is slightly telegraphic.

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?

An output schema exists, so return values need no explanation, and annotations cover the idempotency/safety profile. Still missing are the skill_slug vs collection_slug exclusivity rule and any note on required permissions, which matter for a creation tool with all-optional parameters.

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 0%, so the description must compensate. It explains the target=my_draft + skill_slug pairing well, but leaves collection_slug undocumented and never states that skill_slug and collection_slug are mutually exclusive despite zero required parameters.

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 and resource: 'Create a 15-minute signed download' scoped to 'one granted Ready skill or collection.' It is clearly distinct from siblings like get_install_instructions or get_skill, though it never names an alternative explicitly.

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 a concrete conditional: use target=my_draft with skill_slug to test the authenticated author's unreviewed Draft, which implicitly means ready targets are for published artifacts. It stops short of naming any sibling tool for comparison.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources