get_subnet_calculate
Calculate subnet information from CIDR notation.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cidr | Yes |
ProfitCollector
by ca.bakhour
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of disclosing behavior. It does not mention what subnet information is returned, how invalid CIDR input is handled, or whether IPv4/IPv6 are supported. The description adds no behavioral context beyond the tool's name.
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?
The description is a single, front-loaded sentence with no filler. It communicates the essential operation efficiently and wastes no words.
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 annotations and no output schema, the description leaves return values and behavioral outcomes undefined. It is minimal enough that an agent must guess what 'subnet information' includes and whether edge cases like malformed CIDR are handled.
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 compensate. It only repeats 'CIDR notation,' which adds little beyond the parameter name 'cidr.' No format examples, constraints, or clarification of expected values are given.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action ('Calculate subnet information') applied to a specific input ('CIDR notation'). It distinguishes itself from the sibling tools because no other sibling is dedicated to subnet calculation, so the purpose is unambiguous.
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 guidance on when to use this tool vs alternatives, no prerequisites, and no exclusions. The description implies usage only through its purpose statement, which is not enough to help an agent decide between this and related network utilities.
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.
TDQS
C2.7/5.0
Disambiguation2/5
Multiple tools occupy the same security-audit space: get_dns_lookup/get_domain_intelligence, get_security_posture/get_web_audit/post_domain_due_diligence, and the three post_security_repo_risk_report variants heavily overlap. Video generation is split only by duration, and get_ssl_check/get_security_posture both target TLS/certificate concerns, so an agent could easily select the wrong tool.
Naming Consistency3/5
All tools use snake_case and a get_/ post_ prefix, which is a recognizable convention and generally readable. However, the suffix order is inconsistent (get_url_parse vs get_security_posture vs post_security_repo_risk_repport_standard), and get/post are HTTP-style prefixes rather than semantic verbs, so the pattern is only partially coherent.
Tool Count2/5
34 tools is well above the 'too many' threshold and spans unrelated domains: domain security, repo risk, JSON/hash/text utilities, media generation, Quebec invoices, and x402 payments. Many tools are variants that could be consolidated (video durations, risk report tiers, audit scopes), so the count feels inflated rather than purposeful.
Completeness2/5
The set lacks a single apparent domain, so no complete lifecycle is clearly covered: video generation has no status/retrieval, repo risk reporting is read-only, and common companions (URL encoding, current timestamp, image analysis) are missing. It is a broad collection of one-off utilities rather than a coherent functional surface.