Skip to main content
Glama
Sign In
Copilot Desktop MCP

Copilot Desktop MCP

by avianhermana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Read Image Text

read_image_text
Read-only

Extract text from images and screenshots using OCR to read diagrams, scanned forms, and visual content.

Instructions

Extract text from an image (.png/.jpg/.jpeg/.bmp/.webp) using OCR (Tesseract). Useful for reading screenshots, diagrams, and scanned forms.

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": {
      "path": "<path>"
    },
    "name": "read_image_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
languagesNoeng+ind
max_charsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read; the description's real contribution is naming the OCR engine and the accepted image extensions, which is useful context. It says nothing about accuracy limits, language handling, truncation behavior, or what happens with unsupported inputs, so the added behavioral depth is modest.

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?

Two short sentences, front-loaded with the action and mechanism, followed by a concrete use-case line. Nothing is wasted or repetitive.

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-shape explanation is not needed, and the format list covers input types. The gap is parameter behavior: with zero schema descriptions, the description should at least note that languages affects OCR language selection and max_chars caps output length.

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?

Schema description coverage is 0% across three parameters, and the description mentions none of them. The undocumented 'languages' default ('eng+ind') and the 'max_chars' truncation limit (20000) are exactly the kinds of semantics the description should supply and does not, leaving the agent to guess their effect.

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?

The description names a specific verb+resource ('Extract text from an image') and pins the mechanism (OCR via Tesseract) plus the supported formats, which clearly separates it from generic readers like read_file or read_document. It stops short of explicitly contrasting itself with those siblings, so it is clear but not sibling-differentiated.

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?

'Useful for reading screenshots, diagrams, and scanned forms' implies the usage context but never states when to pick this over read_document or read_file, nor any exclusions. Usage is inferable rather than directed.

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