Skip to main content
Glama
yogendhra9

Zerodha Trading Bot

by yogendhra9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

addition

Add two numbers to calculate trading values for the Zerodha Trading Bot, enabling precise financial computations in automated stock trading operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Implementation Reference

  • index.js:32-34 (registration)
    Registration of the 'addition' tool, including inline schema {a: z.number(), b: z.number()} and handler that returns the sum of a and b as text content.
    server.tool("addition", { a: z.number(), b: z.number() }, async ({ a, b }) => ({
  content: [{ type: "text", text: `${a + b}` }],
}));
  • index.js:32-34 (handler)
    Inline handler function for the 'addition' tool that computes a + b and formats it as MCP content.
    server.tool("addition", { a: z.number(), b: z.number() }, async ({ a, b }) => ({
  content: [{ type: "text", text: `${a + b}` }],
}));
  • index.js:32-32 (schema)
    Input schema for the 'addition' tool using Zod: numbers a and b.
    server.tool("addition", { a: z.number(), b: z.number() }, async ({ a, b }) => ({

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / a
      Added value: +{
+  "type": "number"
+}
    • addedInput schema / properties / b
      Added value: +{
+  "type": "number"
+}
    • addedInput schema / required
      Added value: +[
+  "a",
+  "b"
+]
  2. First observed

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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