Skip to main content
Glama

Build a Monday-first month grid

bpj_calendar_month_layout
Read-onlyIdempotent

Arrange a calendar month in Monday-first rows with null padding.

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": "bpj_calendar_month_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
monthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value by disclosing the output convention (Monday-first, null padding), but with no output schema it does not say how the grid is represented — number of rows, whether weeks are nested arrays, or how many null cells to expect.

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

Conciseness5/5

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

A single front-loaded sentence with the layout convention stated last and no wasted words. Nothing is redundant or buried.

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?

With no output schema and no parameter documentation, the description is the only source of return-value meaning, and it only hints at the shape. For a grid-construction tool an agent still cannot predict the concrete return type or row count.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden, yet it adds nothing about the two parameters beyond implying a month is involved. It does not clarify the year range intent, month numbering, or behavior on out-of-range input beyond what the schema's min/max already encode.

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

Purpose4/5

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

States a specific verb ('Arrange') and resource ('a calendar month') plus the layout constraint ('Monday-first rows with null padding'), which is enough to tell it apart from siblings like bpj_calendar_month_slices or bpj_calendar_iso_week_to_monday. It stops short of naming an alternative or the expected return structure.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of any sibling as an alternative. The agent must infer the use case purely from the one-line purpose statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.