Skip to main content
Glama
Sign In
vision-bridge-mcp

vision-bridge-mcp

by G12789
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

OCR extract text

extract_text

Extract verbatim text from screenshots, logs, or images using OCR. Provide a local path, URL, or data URI to retrieve readable text.

Instructions

OCR for screenshots/logs. Use when you need verbatim text from an image.

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": {
      "source": "<source>"
    },
    "name": "extract_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesLocal path, http(s) URL, or data:image/... URL
contextNo
questionNoSpecific question about the image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.7/5.0
Behavior2/5

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

No annotations provided, and description does not disclose any behavioral traits beyond OCR. No mention of limitations, safety, or side effects, leaving the agent underinformed.

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?

Extremely concise with two sentences that front-load the core purpose. No unnecessary words.

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?

Given no output schema and minimal annotations, the description is too brief. It does not explain return values, error cases, or how to use the optional context and question parameters effectively.

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 coverage is 67% with two of three parameters described. Description adds no extra meaning beyond the schema; context parameter remains undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it is an OCR tool for screenshots/logs to extract verbatim text. Distinguishes from sibling tools like compare_images and describe_image.

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?

Explicitly says 'Use when you need verbatim text from an image,' providing clear usage context. Lacks explicit when-not-to-use or alternative mention, but still functional.

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