Retrieves a security's current quote from Scalable Capital by ISIN. Optionally includes year-to-date performance and portfolio-specific data for informed investing decisions.
Get the current Scalable Capital quote for a security by ISIN.
| Name | Required | Description | Default |
|---|---|---|---|
| isin | Yes | ||
| include_ytd | No | ||
| portfolio_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It clearly implies a read-only quote lookup, but it does not disclose quote freshness, data source, authentication expectations, or error behavior. The core behavior is transparent enough for a simple lookup, but additional context is missing.
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?
One concise sentence, front-loaded with the action and resource, with no filler or redundant information.
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?
The description covers only the core lookup behavior and the required parameter. It omits any explanation of the two optional parameters and does not provide enough context for an agent to know when to set them. Though an output schema exists, the optional-parameter gap leaves the definition incomplete.
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?
Only the 'isin' parameter is meaningfully explained, and only incidentally through the phrase 'by ISIN.' The optional 'include_ytd' and 'portfolio_id' parameters are completely undocumented, and schema description coverage is 0%, so the description does not compensate for the gap.
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 specifies a clear verb and resource: 'Get the current Scalable Capital quote for a security by ISIN.' It is distinct from the sibling tools in function, but it does not explicitly differentiate itself from alternatives like sc_search or sc_holdings.
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?
Usage is only implied: if an agent needs a current quote by ISIN, this is the tool. There is no explicit guidance on when to use this over siblings, nor any mention of related lookup tools such as sc_search.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.