Find BCSE shares/bonds by ticker substring; returns entity_type and TokenBel uuid for detail or trading tools. Tokens have no tickers. Example: {"query":"ASB"}.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Result cap; default 20 (max 100). | |
| query | Yes | Case-insensitive share/bond ticker substring. |
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | ||
| query | Yes | ||
| results | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / limit / descriptionPrevious value: -"Max results (1-100, default 20)"New value: +"Result cap; default 20 (max 100)."Input schema / properties / query / descriptionPrevious value: -"Ticker search query for listed shares/bonds only (case-insensitive substring, e.g. 'MTB' matches 'MTBank')"New value: +"Case-insensitive share/bond ticker substring."Output schema / properties / results / items / properties / admission_date / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / results / items / properties / admission_date / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / results / items / properties / currency / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / results / items / properties / currency / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / results / items / properties / is_trading / anyOfRemoved value: -[
- {
- "type": "boolean"
- },
- {
- "type": "null"
- }
-]Output schema / properties / results / items / properties / is_trading / typeAdded value: +[
+ "boolean",
+ "null"
+]Output schema / properties / results / items / properties / issuer_name / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / results / items / properties / issuer_name / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / results / items / properties / kind / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / results / items / properties / kind / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / results / items / properties / nominal_value / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / results / items / properties / nominal_value / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / results / items / properties / ticker / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / results / items / properties / ticker / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "count": {
+ "type": "number"
+ },
+ "query": {
+ "type": "string"
+ },
+ "results": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "admission_date": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "currency": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "entity_type": {
+ "enum": [
+ "share",
+ "bond"
+ ],
+ "type": "string"
+ },
+ "is_active": {
+ "type": "boolean"
+ },
+ "is_trading": {
+ "anyOf": [
+ {
+ "type": "boolean"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "issuer_name": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "issuer_uuid": {
+ "anyOf": [
+ {
+ "description": "TokenBel internal identifier: opaque hexadecimal string, usually 8 characters such as \"78c7e502\"; despite uuid field names, it is not an RFC UUID and normally has no hyphens.",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "kind": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "nominal_value": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "ticker": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "uuid": {
+ "description": "TokenBel internal identifier: opaque hexadecimal string, usually 8 characters such as \"78c7e502\"; despite uuid field names, it is not an RFC UUID and normally has no hyphens.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "entity_type",
+ "uuid",
+ "ticker",
+ "kind",
+ "issuer_uuid",
+ "issuer_name",
+ "nominal_value",
+ "currency",
+ "is_trading",
+ "is_active",
+ "admission_date"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "results",
+ "count",
+ "query"
+ ],
+ "type": "object"
+}Input schema / properties / query / descriptionPrevious value: -"Ticker search query (case-insensitive substring, e.g. 'MTB' matches 'MTBank')"New value: +"Ticker search query for listed shares/bonds only (case-insensitive substring, e.g. 'MTB' matches 'MTBank')"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, so the safe read-only nature is covered. The description adds value beyond annotations by disclosing substring matching behavior, stating what the result supplies (entity_type and TokenBel uuid), and clarifying the token limitation. This is useful behavioral context without redundancy.
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?
The description is compact and front-loaded: the action and scope appear in the first sentence, followed by output purpose, a key exclusion, and a concrete example. Every sentence adds useful information with no filler.
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 lookup tool with fully documented parameters, read-only annotations, and an output schema, the description provides all necessary context: what it searches, what it returns, how to use the result, and an important domain limitation. No essential information is missing for correct invocation.
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 description coverage is 100%, so both query and limit are already documented in the schema. The description reinforces 'ticker substring' and provides an example query, but it does not materially expand parameter meaning beyond what the schema already states. A baseline 3 is appropriate.
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 opens with a specific verb and resource: 'Find BCSE shares/bonds by ticker substring.' It also distinguishes itself from search_by_name by specifying the lookup key (ticker rather than name) and from token tools by noting 'Tokens have no tickers.' This makes the tool's purpose immediately identifiable.
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?
The description provides clear usage context: it is for locating shares/bonds by ticker substring and returning UUIDs for downstream detail or trading tools. It also states an exclusion ('Tokens have no tickers') that prevents misuse. It does not explicitly name search_by_name as the alternative for name-based lookup, but the context is strong enough to guide selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.