Skip to main content
Glama
Sign In
camcors-mcp

camcors-mcp

by Davidobot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Open CamCORS

camcors_open
Read-onlyIdempotent

Opens a persistent Chrome session to check CamCORS authentication and prompt Raven login if unauthenticated.

Instructions

Open the local persistent Chrome session and report whether CamCORS is authenticated. If login is required, the user completes Raven authentication in the opened browser.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is known. The description adds behavioral context by explaining that it reports authentication and triggers user interaction if login is needed. This goes beyond annotations without contradicting them.

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?

The description is two sentences long, front-loaded with the main action, and every word adds meaning. No redundancy or fluff.

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?

The description does not mention the return value format (e.g., boolean or string), nor does it cover potential failure modes (e.g., Chrome not found). For a simple tool with no output schema, these gaps reduce completeness.

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?

There are no parameters, and schema coverage is trivially 100%. Per guidelines, baseline for 0 params is 4. The description does not need to add parameter details since none exist, and it adds value by describing the tool's action.

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 description clearly states the verb 'Open' and the resource 'local persistent Chrome session', and distinguishes this tool from sibling tools that deal with reports and submissions. It explicitly says it reports authentication status, making the purpose unmistakable.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. While it implies it is a prerequisite for other CamCORS operations, it does not explicitly state that or mention any exclusions or preferred contexts.

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