RegusciLabs Documentation

get_latest_activity

Read-onlyIdempotent

Browse curated public RegusciLabs social posts with real post URLs, platform, language, topic and verified-date filters and pagination. Not a real-time feed; unverified post dates are null and platforms without approved sources may be empty.

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_latest_activity"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No	Only posts with verified dates can match this upper bound.
`from`	No	Only posts with verified dates can match this lower bound.
`limit`	No
`topic`	No	Match only public titles, summaries, tags and approved project names.
`cursor`	No	Reuse nextCursor with identical filters.
`locale`	No		all
`platform`	No		all

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: results are curated/approved-source only, unverified post dates are returned as null, and some platforms may return empty — real expectations an agent would otherwise miss.

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 tight sentences with no filler; the positive capability statement is front-loaded and the two caveats follow. Slightly dense but every clause carries information.

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?

With no output schema, the description does the work of setting result expectations (curated, nulls for unverified dates, possibly empty platforms) and covers the filter surface at a high level. Complete enough to call correctly, though limit/locale behavior remains undocumented across both description and schema.

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 57%, with to/from/topic/cursor documented in the schema itself. The description names the filter categories (platform, language, topic, verified-date, pagination) but adds no syntax or semantics for the undocumented limit and locale parameters, and its 'verified-date' note largely restates the schema.

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 ('Browse') and resource ('curated public RegusciLabs social posts') with the filter set, so an agent immediately knows this returns social posts rather than news or raw records. It does not explicitly contrast with siblings like get_latest_news or search_information, so it falls short of a 5.

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

Usage Guidelines3/5

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

Use is implied by 'curated public ... social posts' plus the caveat 'Not a real-time feed', which steers the agent away from expecting live data. However, there is no explicit when-to-use guidance or routing to the sibling tools (get_latest_news, search_information) for other content types.

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

All RegusciLabs Documentation 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?