Skip to main content
Glama
finnhyun12

genicam-mcp

by finnhyun12

discover_cameras

Discover available cameras by enumerating all registered producers. Returns camera index, vendor, model, serial number, and transport type (e.g., U3V, GEV) for connection via connect(index).

Instructions

등록된 producer 전체에서 연결 가능한 카메라를 열거한다.

각 항목의 index 를 connect(index) 에 넘긴다. 벤더/모델/시리얼/전송규격
(tl_type: U3V, GEV 등)을 함께 돌려준다. 0대가 나오면 카메라 전원·케이블과
등록한 .cti 가 그 카메라의 전송규격과 맞는지 확인하라.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses behavior: it's a read-only discovery enumeration, returns specific data, and provides troubleshooting steps. No hidden side effects or contradictions.

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 sentences: first states purpose, second provides usage instructions and output details. All information is essential, no fluff. Front-loaded with key action.

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?

Given the presence of an output schema, the description covers the tool's role comprehensively: what it does, how to use the result, and troubleshooting for empty results. Meets all needs for a no-parameter tool.

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 zero parameters, and schema coverage is 100%. The description does not need to explain parameters; it focuses on output and usage, which is appropriate. Baseline for 0 params is 4.

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 it enumerates connectable cameras from registered producers, specifying the output includes vendor/model/serial/transport type. It differentiates from sibling tools like connect (which uses the index) and list_features.

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

Usage Guidelines5/5

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

Explicitly instructs to use the index from this tool with connect(index). Provides diagnostic advice when zero cameras are returned: check power, cable, and .cti transport type match. No ambiguity about when to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/finnhyun12/genicam-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server