Skip to main content
Glama
Socifyr MCP

Socifyr MCP

by Socifyr

get_usage

Show current workspace usage against plan limits, including monthly posts, connected accounts, and storage, so you can check remaining quota before connecting accounts or publishing posts.

Instructions

Show the workspace's current usage against its plan limits: posts this month, connected accounts, and storage. Check this before connecting accounts or posting to see remaining quota.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. "Show" plus "remaining quota" makes clear this is a non-mutating read of plan state, which is useful context. It does not say whether figures are real-time or cached, whether the response includes limit values alongside usage, or what it returns when a limit is already exceeded.

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?

Two short sentences with the payload front-loaded: what it reports, then when to call it. No filler or restatement of the tool name. Only minor tightening would improve it.

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

Completeness4/5

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

For a zero-parameter read tool with no annotations and no output schema, the description does the heavy lifting by naming the three metrics returned, which substitutes for a missing output schema. It is complete enough to call correctly, with only response format and freshness left unspecified.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The sentence does usefully imply that scope is fixed to the current workspace with no filtering options, which is worth stating.

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 and resource ("Show the workspace's current usage against its plan limits") and enumerates the three metrics returned: posts this month, connected accounts, storage. That enumeration distinguishes it from the analytics siblings (get_post_analytics, get_follower_growth), which report performance rather than quota consumption, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

Gives an explicit trigger: "Check this before connecting accounts or posting to see remaining quota." That is a concrete when-to-use rule tied to two sibling actions (list_connections/reconnect_connection and post_*). It stops short of a when-not-to-use statement or a named alternative, which keeps it off a 5.

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