Skip to main content
Glama
Sign In
Tipsoi MCP

Tipsoi MCP

by the-abraar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

monthly_overtime_report

Read-only

Get monthly overtime report for a given year and month. Supports filtering by office and company for targeted analysis.

Instructions

Monthly overtime report.

Args: year: e.g. 2026. month: 1-12. office_id: Falls back to TIPSOI_OFFICE_ID. company_id: Falls back to TIPSOI_COMPANY_ID. per_page: Pagination size.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": "<year>",
      "month": "<month>"
    },
    "name": "monthly_overtime_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
monthYes
office_idNo
company_idNo
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true. Description adds only the fallback behavior for office_id and company_id, but no details on pagination outcomes, error handling, or data scope.

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

Conciseness4/5

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

Extremely short and front-loaded with 'Monthly overtime report.' followed by a clear Args list. No redundant text.

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

Completeness2/5

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

No output schema or description of return values, leaving the agent uncertain about what data the report includes. Fails to differentiate from sibling reports.

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

Parameters3/5

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

Schema description coverage is 0%, so description compensates with examples ('year: e.g. 2026'), range ('month: 1-12'), and fallback behavior. However, per_page is vague ('Pagination size') and no detailed format expectations.

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

Purpose2/5

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

Description is just a noun phrase 'Monthly overtime report.' It lacks a verb indicating the action (e.g., 'generate', 'view'). It does not distinguish from sibling report tools like monthly_attendance or late_report.

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?

No guidance on when to use this tool versus alternatives. Sibling tools include many similar reports, and the description provides no context for selection.

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