Sentrint

Show scans left

sentrint_get_allowance

Read-only

Show how many scans this account can still start: what is left of the plan's allowance this period, scan credits the user bought, and how many of today's 20 scan starts from AI apps are used. Call it before sentrint_scan_repo when the user is on the free plan or may be near a limit; reading it costs nothing. can_start_new_scan is false when a new commit would be refused, and next_step says why.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`plan`	Yes	The plan the account is on, such as Free or Founder.
`period`	Yes	How often the plan's allowance resets: day or month.
`next_step`	Yes	What to do next, in a sentence written for the agent.
`scan_credits`	Yes	Scan credits bought, used once the plan runs out.
`mcp_daily_limit`	Yes	Most scans AI apps can start in one UTC day.
`mcp_scans_today`	Yes	Scans started from AI apps today, UTC.
`can_start_new_scan`	Yes	False when sentrint_scan_repo would refuse a new commit right now.
`scan_limit_in_period`	Yes	The plan's scans per month; null for plans not counted monthly.
`scans_used_in_period`	Yes	Scans used from the plan this period.
`free_allowance_blocked`	Yes	True when the free scan waits on the account's age.
`included_scans_remaining`	Yes	Scans left in the plan this period.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new behavior — that the call consumes no quota and that can_start_new_scan=false means a new commit would be refused. It stops short of describing anything about the shape or pagination of the response, but that is largely the output schema's job.

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?

Two tight sentences: the first defines the payload, the second gives the call condition and the meaning of the key outcome fields. The most decision-relevant information (when to call, cost) is front-loaded in the second sentence rather than buried.

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

Completeness5/5

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

An output schema exists, so return values need not be documented, yet the description still surfaces the two fields that drive agent behavior (can_start_new_scan, next_step). For a zero-parameter read tool this covers everything needed to call it correctly and interpret the answer.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly avoids inventing parameter discussion and spends its words on return semantics instead.

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?

States a specific verb and resource ('show how many scans this account can still start') and enumerates the three components of the allowance: plan remainder, purchased credits, and daily AI-app starts. It is clearly distinguishable from siblings like sentrint_list_scans and sentrint_scan_repo, which consume or enumerate scans rather than report remaining capacity.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Call it before sentrint_scan_repo when the user is on the free plan or may be near a limit') and names the alternative it precedes. It also removes cost hesitation with 'reading it costs nothing', so the agent knows there is no downside to checking first.

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

All Sentrint tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?