Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Set how scans are read

files_ocr_settings
Idempotent

auto_ocr: read every new scan (an image, or a PDF without text) with OCR as it arrives, $0.005 a page, charged from the balance; a scan the balance can't cover stays unread and says why. Off by default: scans are then read when you ask (files_ocr). languages: the ones OCR reads in, up to 3 ([] goes back to the account's language: its website's, else its country's, else English). $0.001. Costs $0.001 per call; nothing if it fails.

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": "files_ocr_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
auto_ocrNo
languagesNoUp to 3 of eng, deu, fra, spa, ita, nld, por, swe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: per-page and per-call costs, failure non-charging, default-off behavior, balance-related unread scans, and language fallback rules. These details are directly useful for an agent deciding whether and how to mutate OCR settings.

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?

The text is dense and front-loads the two settings, with each sentence carrying useful cost or behavior information. It is somewhat run-on, especially around the repeated cost figures, but not verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter settings mutation with no output schema, the description covers defaults, costs, failure behavior, language fallback, and the on-demand alternative. An agent has enough information to invoke it correctly and understand its operational impact.

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

Parameters4/5

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

Schema coverage is only 50%, but the description compensates well by fully explaining auto_ocr's effect and by adding meaning to languages beyond the schema's enum list, including the three-language limit and empty-array reset behavior. The remaining gap is minor because the schema still supplies the allowed language codes.

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?

The definition clearly identifies the resource as OCR settings and explains both controllable behaviors: automatic OCR of new scans and preferred OCR languages. It also contrasts automatic reading with on-demand reading via files_ocr, so an agent can distinguish it from the sibling tool without opening the schema.

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?

It explains that auto_ocr is off by default and that scans are then read on request through files_ocr, which gives clear context for when this settings tool is relevant. It does not explicitly say 'use this tool when...' or list exclusions, but the usage path is strongly implied.

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

All Conecto toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources