Retrieve the current value of a variable or parameter visible in IC-CAP's Main context by name, searching through variables, parameters, table variables, and datasets.
Get a variable or parameter value visible from Main (searches hierarchy: variables, parameters, tablevars, datasets).
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Variable or parameter name |
Changes observed during successful MCP inspections.
v0.2.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
It discloses a useful behavioral trait: the hierarchy search order. However, with no annotations, the description carries the full burden and does not state return format, failure behavior when the name is not found, or explicitly confirm the operation is read-only (though 'get' implies it).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with the action and resource front-loaded, followed by a compact parenthetical that adds the search-order detail. No redundant wording.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter getter, the description covers the main purpose and scope well. However, since there is no output schema, the description should more explicitly convey return behavior and what happens when the name is not visible; these gaps remain.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description adds context that the name parameter refers to a Main-visible variable or parameter, but it does not add syntax details like name formatting or path handling beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Get'), a concrete resource ('variable or parameter value'), and a clear scope ('visible from Main'), plus the search hierarchy. This clearly distinguishes it from object-scoped getters like object_get_valof.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides clear context for when to use the tool: when retrieving a value by name from Main across variables, parameters, tablevars, or datasets. It does not explicitly name alternatives or exclusion conditions, but the Main-scoped framing is a sufficient selection signal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.