Skip to main content
Glama

get_script

Read-only

Reads a saved script so you can edit it, returning the editable body for saved scripts or the full file for imported ones.

Instructions

Read a saved script, to change it. Returns the editable body for scripts you saved, or the whole file for imported ones.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description is consistent with that. It adds genuinely useful behavior beyond the annotations: return payload differs by script provenance, editable body for user-saved scripts versus whole file for imported ones. It does not cover missing-script behavior, but the provenance distinction is substantive.

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 short sentences with the core action front-loaded and the return-value caveat second. The phrasing 'Read a saved script, to change it' is slightly awkward, but no sentence is wasted.

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?

For a one-parameter read with no output schema, the description usefully characterizes the returned content and its two shapes. It still leaves the parameter meaning and not-found behavior unspecified, which matters for an agent constructing a call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter 'name' has 0% schema description coverage, so the description must carry the burden and does not. It never clarifies whether 'name' is the script title, an identifier, case-sensitive, or how to obtain a valid value — the reference to 'scripts you saved' only loosely implies a name lookup.

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 ('Read') and resource ('saved script') and hints at the edit workflow. It distinguishes itself implicitly from list_scripts, run_script, and save_script by framing the tool as fetching content for modification, though it never names a sibling.

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

Usage Guidelines3/5

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

'to change it' implies the retrieval step of an edit workflow, which is real usage context. However, it gives no explicit when-not guidance, does not name save_script as the follow-up, and does not say how this differs from list_scripts for discovery.

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