Skip to main content
Glama

Scan text

scan_text
Read-onlyIdempotent

Scans inline content such as SKILL.md, MCP tool descriptions, or web-fetched configs for security risks without writing to disk; set kind to apply the relevant rules.

Instructions

Scans content passed inline, such as a SKILL.md, an MCP tool description or an MCP config fetched from the web, without writing it to disk. Set kind to say what the content is. Read-only and offline.

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": {
      "content": "<content>"
    },
    "name": "scan_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWhat the content is; selects the rules that apply.skill
contentYesThe text to scan.
filenameNoName shown in findings. Only its base name is used.
max_findingsNoLargest number of findings to return, most severe first.
min_severityNoLeave out findings below this severity.low

Output Schema

NameRequiredDescriptionDefault
toolYes
countsYes
skippedYes
targetsYes
versionYes
completeYesFalse when some files or folders were not scanned; a scan that is not complete is not a clean result.
findingsYes
filesScannedYes
skippedFilesYes
highestSeverityYes
omittedFindingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.1
    • addedOutput schema / properties / complete
      Added value: +{
      +  "description": "False when some files or folders were not scanned; a scan that is not complete is not a clean result.",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / skipped
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "path": {
      +        "type": "string"
      +      },
      +      "reason": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "path",
      +      "reason"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "tool",
      -  "version",
      -  "filesScanned",
      -  "targets",
      -  "counts",
      -  "highestSeverity",
      -  "findings",
      -  "omittedFindings",
      -  "skippedFiles"
      -]New value: +[
      +  "tool",
      +  "version",
      +  "filesScanned",
      +  "targets",
      +  "counts",
      +  "highestSeverity",
      +  "findings",
      +  "omittedFindings",
      +  "skippedFiles",
      +  "complete",
      +  "skipped"
      +]
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint=false, idempotentHint and destructiveHint=false, so 'Read-only and offline' largely repeats structured data. The genuinely additive fact is that content is never written to disk, which is useful for an agent handling untrusted web-fetched config, but nothing is said about result shape or how findings are ordered/truncated.

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?

Three short sentences, front-loaded with the core action and scope, with no filler. 'Read-only and offline' is slightly redundant against the annotations but is not wasteful enough to penalize heavily.

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?

With a full output schema and complete annotations, the description need only clarify scope and safety-relevant behavior. It covers inline-vs-disk and gives representative content types, leaving only minor gaps like how findings are truncated relative to max_findings.

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 all five parameters are already documented in the schema. The description only restates the purpose of kind ('say what the content is'), adding no syntax, enum guidance, or interaction detail beyond the structured fields.

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 (scans) and resource (content passed inline) with concrete examples (SKILL.md, MCP tool description, MCP config). The inline-content scope implicitly separates it from scan_path/scan_installed, but the sibling tools are never named, so differentiation is left to inference.

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?

The phrase 'content passed inline... without writing it to disk' implies when to use this over file-based scanning, and 'Set kind to say what the content is' is a usage instruction. However, there are no explicit when/when-not statements and no named alternatives among the siblings.

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